InfoPath Dev

Thanks, Anson.  I wasn't clear.  I do realize that the property promotion doesn't factor into the list case.  I guess my question is whether anyone can explain how InfoPath is able to populate those Person fields in the list scenario?  Is it just writing the accountID as text and SP is resolving the name?

I've seen lots of posts about how this isn't possible directly from InfoPath.  Most solutions suggest saving the AccountID as text and then using a SPD workflow to set the Person/Group field in SharePoint.  Can anyone explain why/how this works if I create a SP list, add a Person/Group field and then Customize the list ...