BuilderVault
FreeAdvancedPower AppsPower AppsSharePoint

Patch a SharePoint multi-person field

Learn how to use Power Apps Patch a SharePoint multi-person field with practical Power Apps guidance, implementation steps, common mistakes, troubleshooting, and related BuilderVault patterns.

Power Apps Patch a SharePoint multi-person fieldhigh intentAdvanced

What this pattern solves

Power Apps Patch a SharePoint multi-person field is a practical BuilderVault pattern for makers and developers who need a repeatable way to handle patch a sharepoint multi-person field inside a real Microsoft business app. The goal is to move past trial-and-error and give the builder a clear structure they can adapt to their own screens, flows, lists, tables, or environments.

Use this page when you are deciding how the pattern should work, what supporting data or permissions are needed, and what should happen when the happy path fails. The notes below focus on implementation fit, common mistakes, troubleshooting, and internal links to adjacent patterns so the build stays consistent.

Search intent

Help a Power Platform builder understand when to use Power Apps Patch a SharePoint multi-person field, how to implement it, and what mistakes to avoid before using it in a production business app.

Problem

Multi-person SharePoint fields require a table of expanded user objects, not a list of emails or display names.

What the finished pattern should include

  • A maker can explain the control, formula, validation, and save behavior before release.
  • The app gives users clear feedback for successful saves, missing values, and failed updates.
  • The pattern can be handed to another builder without relying on hidden assumptions.

Solution

Formula / code
Patch(
    Requests,
    selectedRequest,
    {
        Reviewers: ForAll(
            cmbReviewers.SelectedItems,
            {
                '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
                Claims: "i:0#.f|membership|" & Lower(Mail),
                DisplayName: DisplayName,
                Email: Mail,
                Department: "",
                JobTitle: "",
                Picture: ""
            }
        )
    }
)

Implementation checklist

  • Confirm the Power Apps scenario and the business user this pattern supports.
  • Identify the data source, owner, security model, and exception path before building.
  • Build the smallest reusable version first, then add optional branches or polish.
  • Test with realistic data, permissions, edge cases, and handoff expectations.
  • Link this pattern to its collection, topic hub, and related implementation patterns.

Step-by-step instructions

  • Confirm the SharePoint person column allows multiple selections.
  • Use a user source that returns Mail and DisplayName.
  • Transform each selected user into an expanded user record.
  • Patch the resulting table to the person field.

When to use

  • Reviewer lists
  • Multiple approvers
  • Stakeholder fields

When not to use

  • Security trimming that should be handled with Microsoft 365 groups
  • Large audience fields

Common mistakes

  • Reusing the single-person patch object without wrapping it in a table.
  • Using email addresses without claims.
  • Not clearing optional Department or JobTitle fields.

Troubleshooting

  • If SharePoint rejects the value, check that every selected user has a Mail value.
  • If defaults do not load, compare the saved table schema to the combo box Items schema.

FAQ

When should I use Power Apps Patch a SharePoint multi-person field?

Use Power Apps Patch a SharePoint multi-person field when the same Power Apps scenario is likely to appear in more than one app, flow, list, table, or environment and needs a repeatable implementation approach.

Does this pattern work with Power Apps, SharePoint?

Yes. This pattern is written for Power Apps, SharePoint scenarios, but you should still confirm connectors, licensing, permissions, delegation limits, and environment rules before using it in production.

What usually causes this Power Apps pattern to fail?

The most common failure points are unclear ownership, missing validation, weak exception handling, undocumented permissions, and testing only the happy path.

Is Power Apps Patch a SharePoint multi-person field beginner friendly?

This pattern is rated Advanced. Beginners can use the fit guidance and checklist first, while experienced builders can move directly into the formula, flow, schema, or governance details.

Related patterns