Builder review7 min readUpdated June 5, 2026

People picker and person-like fields

Choose how to handle InfoPath person fields, role lists, email fields, and SharePoint Person columns.

Quick answer

In short

People fields need extra review because InfoPath may have stored display names, emails, account IDs, or role-list values that are not the same as a SharePoint Person column.

Most likely cause

Generated apps often look correct but save the wrong identity value if the source form displayed a name and saved an email or account key.

What to do next

Decide whether the target should be a SharePoint Person column, text display name, email text field, or a supporting role-list dropdown.

Common source patterns

  • InfoPath Contact Selector or people picker.
  • A User Roles list where dropdowns display Name and save Email.
  • Text fields that store display names only.
  • Hidden fields that store account IDs, emails, or claims-like values.

Flatten or preserve identity

Flatten to text/email when the app only needs to display or notify a person. Use SharePoint Person columns when the app needs directory-aware people selection, profile cards, or person-column filtering.

Test cases

  1. Select a user in the generated app.
  2. Submit the item.
  3. Confirm SharePoint stores the expected value type.
  4. Open the record again and confirm the selected person displays correctly.
  5. Test with a different user account if permissions or claims formatting may differ.

Keep reading the next most relevant guides for this form pattern.