https://www.infopathdev.com:443/forums/40.aspxFor browser form specific questionsenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/118150.aspxFri, 19 Jan 2018 23:10:51 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:118150Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/118150.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=118150<p>&nbsp;I would probably drag the repeating group for the person picker onto the form someplace as a repeating table so you can verify all the values are being populated as anticipated. </p>https://www.infopathdev.com:443/forums/thread/118047.aspxWed, 10 Jan 2018 15:02:10 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:118047bkwhodgson0https://www.infopathdev.com:443/forums/thread/118047.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=118047<p>A user is developing an InfoPath form, that is published to a SharePoint form library in SharePoint Online. There is a person picker field, set by a form load rule (on condition the field is blank)&nbsp;to be the current user (using the username() function). When using the form this works fine and upon the form opening the current user&#39;s name is in the person picker field. This field is&nbsp;a promoted field to a column called Display Name (wit the Display Name property of the person picker group of fields). However despite the field clearly being filled in, when an instance of the form is saved to SharePoint, the Display Name column is blank.</p><p>Before&nbsp;using this rule, the field would be manually populated and the SharePoint column would be populated as well.</p><p>I set up a test form to recreate the error, but my test was successful. The only&nbsp;difference was I&#39;m a global admin, the user is only a site admin.</p><p>Does anybody have any ideas why the form load rule is appearing to work&nbsp;when using the form - but then doesn&#39;t promote to SharePoint?&nbsp;</p>