Answered

People Value Not Getting Written to SharePoint Column

(1) Share

Report

Posted on by LE-18020725-0

Hello,

I have an issue which I hope someone can assist me. I have built a Power platform solution which is made up of 2x SharePoint Lists, 1x Canvas App, 1x Flow, and the connectors. When I am submitting the form on the canvas app, The people column fields data are not writting to the SharePoint List columns.

Below are are settings on the canvas app;

DataCard properties:

Update;

If(
IsBlank(DataCardValue24.Selected.Mail),
Blank(),
{
'@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims: "i:0#.f|membership|" & Lower(DataCardValue24.Selected.UserPrincipalName),
DisplayName: DataCardValue24.Selected.DisplayName,
Email: DataCardValue24.Selected.Mail
}
)

Default;

ThisItem.Next_Approving_Manager_Name
 
DisplayName;
DataSourceInfo([@IT_Services_Application_Dev],DataSourceInfo.DisplayName,'Next_Approving_Manager')
 
DataCardValue properties:
Item;
If(
    IsBlank(Self.SearchText),
    [],
    Office365Users.SearchUser({searchTerm: Self.SearchText})
)
DefaultSelectedItems;
[Parent.Default]
 
Please assist me.

Categories:

Power Apps Pro Dev & ISV

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Sam_Fawzi 917 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @LE-18020725-0,

Is your SharePoint People column single Or multiple person?

Was this reply helpful? Yes No
Suggested answer

wolenberg_ 1,476 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello there,
The structure is right, but the safest fix is to use the Mail property consistently for both Claims and Email. That usually resolves the issue of data not writing back to SharePoint.

This is a common issue when writing People fields back to SharePoint from Power Apps the formula looks close, but a few details can cause the values not to save.

Things to check

Confirm the field type in SharePoint

Make sure the column is set to “Person or Group” and not just a text field.

Use the Office365Users connector consistently

Instead of mixing UserPrincipalName and Mail, try sticking with Mail for both Claims and Email. Example:
{ '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims: "i:0#.f|membership|" & Lower(DataCardValue24.Selected.Mail), DisplayName: DataCardValue24.Selected.DisplayName, Email: DataCardValue24.Selected.Mail }

DefaultSelectedItems

Your [Parent.Default] is fine, but make sure the Default value coming from SharePoint is actually a user record, not just text.

Test with a simple user field

Try binding the card directly to a Person column without custom formulas. If that works, then gradually add back your custom logic.

Was this reply helpful? Yes No
Verified answer

WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @LE-18020725-0,

I need to add a few things here that may assist -

Firstly (a minor issue) you do not need the '@odata.type' reference any more.

You may need three other fields in there (see below)

Your DefaultSelectedItems (which @wolenberg_ touched on) needs to be different if you are using the Office365Users.SearchUser function in the Items of the Combo Box as the schema is different to that of the Person field

So firstly your Data Card Update

{ Claims: "i:0#.f|membership|" & Lower(DataCardValue24.Selected.Mail), Department: "", DisplayName: DataCardValue24.Selected.DisplayName, Email: DataCardValue24.Selected.Mail, JobTitle: "", Picture: "" }

and your DefaultSelectedItems (using your Person Field name)
{ Mail: ThisItem.PersonFieldName.Email, DisplayName: ThisItem.PersonFieldName.DisplayName }

I have a blog on the process of dealing with Person Fields from a Combo Box, which may be of interest to you.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No