Power Apps

Values of People picker in not updating using Patch in Canvas app

(2) Share

Report

Posted on by N962908

I have a control in Canvas app

DefaultSelectedItem : [Parent.Default]

Items :

AddColumns(
    Filter(
        Office365Users.SearchUserV2({searchTerm: DataCardValue9.SearchText}).value,
        !IsBlank(Mail) && AccountEnabled = true
    ),
    FullLabel,
    DisplayName & " (" & Mail & ")"
)
 
Card Update property is : DataCardValue9.Selected
 
I am using Petch to update the selected column value 
 
If( varFormMode = FormMode.New,     
    
                    
                Patch(
                    'SPL_NEJE Template Programming Submission',
                    Defaults('SPL_NEJE Template Programming Submission'),
                    {
                    
                    'BeneComm PM': {'@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
                                    Claims: "i:0#.f|membership|" & Lower(DataCardValue9.Selected.Mail),
                                     DisplayName: DataCardValue9.Selected.DisplayName,
                                     Email: DataCardValue9.Selected.Mail,
                                      Department: "",
                                      JobTitle: "",
                                      Picture: ""
                                    }
                      
                    },
                  
                    Form1.Updates
                   
                    
                    //Attachments_DataCard1.Update
                    
       
                
            )
         
Values is not populating the SP List 'BeneComm PM' column. 
 
What mistake i am doing, any help?
 
Thanks,
        

Categories:

Building Power Apps

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello @N962908,

I guess the issue is because you are updating the same SharePoint Person column in 2 time. Your DataCard Update property is already set to DataCardValue9.Selected and then again you are manually patching the same field inside the Patch function code while also using Form1.Updates.

Try below code:

{ '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims: "i:0#.f|membership|" & Lower(DataCardValue9.Selected.Mail), DisplayName: DataCardValue9.Selected.DisplayName, Email: DataCardValue9.Selected.Mail, Department: "", JobTitle: "", Picture: "" }

So no need to patch the Person field manually again. Just use SubmitForm and try it.

---------------------------------------------------------------------------

Glad it helped 🙂
If this fixed your issue, please click “Does this answer your question?” to mark it as verified so others can find the solution easily.
A Like 👍 is always appreciated, and I’m around if you need more help @Kalathiya

Was this reply helpful? Yes No
Suggested answer

Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello @N962908,

Also, I found another issue in your DefaultSelectedItems property. Record structure must be match the schema returned by your Items property, otherwise the ComboBox will not auto select the default value in form.

Currently both schemas are different, so it will not populate the selected user automatically. In the DefaultSelectedItems property you are using Parent.Default, which has a different schema, and in the Items property you are using Office365Users connection, which returns a different schema. Because of this mismatch, the ComboBox will not select the default value automatically.

Try below code:

LookUp( AddColumns( Filter( Office365Users.SearchUserV2({isSearchTermRequired: false}).value, !IsBlank(Mail) && AccountEnabled = true ), FullLabel, DisplayName & " (" & Mail & ")" ), Mail = _selectedITem.SingleUser.Email ) //_selectedITem - Replace with you variable - Which you have used for store the selected item for edit form.

---------------------------------------------------------------------------

Glad it helped 🙂
If this fixed your issue, please click “Does this answer your question?” to mark it as verified so others can find the solution easily.
A Like 👍 is always appreciated, and I’m around if you need more help @Kalathiya

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @N962908,

Kalathiya is correct that the double-update is the issue. To add the specific reason why it's failing:

When you include both a manual field patch AND Form1.Updates in the same Patch call, the two values for the same column conflict. Power Apps doesn't merge them one overwrites the other, and which one wins depends on evaluation order. In this case Form1.Updates is likely overwriting your manual BeneComm PM value with what the DataCard has stored, which may be in a different format or incomplete.

The clean fix is to choose one approach:

Option 1 (recommended): Remove the manual 'BeneComm PM' patch entirely and just use Form1.Updates. Make sure your DataCard Update property is correct (DataCardValue9.Selected with the right @odata.type format) and let the form handle it.

Option 2: If you need manual Patch control, remove Form1.Updates from the Patch call and manually specify every field you want to update, including BeneComm PM with the @odata.type structure you already have.

Mixing both in the same Patch call is the root cause. Pick one and remove the other.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @N962908,

Firstly @Kalathiya is correct in the core of the issue. I will just add this blog of mine that may be useful for dealing with Person fields and Combo Boxes.

Was this reply helpful? Yes No