cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
abd3127
Kudo Kingpin
Kudo Kingpin

Saving data from powerapps to SP lists person/Group column

Hello ,

i need to save the user info in Person/Groups column of my SP list.

I am selecting the data from a Drop down list.

When i do "DD.selected.value' it gives mee error saying that it needs a record to save.

How can i do this??

1 ACCEPTED SOLUTION

Accepted Solutions
v-micsh-msft
Community Support
Community Support

Hi @abd3127,

 

As the Person or group column type in SharePoint list is considered as a lookup field, we should patch the whole record of the person to this field, and depends on whether you have the Multi-Selection enabled, the schema varies.

I will share an example here.

1. Patch to the Person or group field, which only allows single value.

The record of single person would contain the following values:

 

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Claims:"i:0#.f|membership|michael@wiXXXX.onmicrosoft.com",
    Department:"",
   DisplayName:"Michael Shao",
         Email:"Michael@wiXXXX.onmicrosoft.com",
      JobTitle:"",
       Picture:""
   }

Each value should match the pre-defined value stored under SharePoint data source, if you have no idea for the Department, JobTitle or Picture field, you may just leave it as "".

 

 

Fields need to be entered:

The Value for this field is fixed.

'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",

for Claims field,you should modify the end of this field to match the person Email:

Claims:"i:0#.f|membership|michael@wiXXXX.onmicrosoft.com",

And the DisplayName and Email field, as shown below:

 

 DisplayName:"Michael Shao",
         Email:"Michael@wiXXXX.onmicrosoft.com",

 

To patch a person to the Person or group field as a new record, the formula should be(Title is a required field when creating new records, so whenever a new record is created, all the required field should be get involved in the patch 3rd parameter.):

 

Patch(Patchtesting,
Defaults(Patchtesting), { Title:"SinglePerson", Person: {'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims:"i:0#.f|membership|michael@testing.com", Department:"", DisplayName:"Michael Shao", Email:"Michael@testing.com", JobTitle:"", Picture:"" }})

 

For Person or group Field which have Multiple selection enabled, the structure is a little difference.

For example, the following code would work to patch the MultValue person field:

Patch(Patchtesting,Defaults(Patchtesting),
{ Title:"MultiPerson",
Multi_x002d_Person: Table( { Claims:"i:0#.f|membership|michael@testing.com", Department:"IT", DisplayName:"Michael Shao", Email:"Michael@testing.com", JobTitle:"", Picture:""}, { Claims:"i:0#.f|membership|test2@testing.com", Department:"", DisplayName:"Test2", Email:"Test2@testing.com", JobTitle:"", Picture:""}) } )

Image reference:

47.PNG

48.PNG

46.PNG

 

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

24 REPLIES 24
v-micsh-msft
Community Support
Community Support

Hi @abd3127,

 

As the Person or group column type in SharePoint list is considered as a lookup field, we should patch the whole record of the person to this field, and depends on whether you have the Multi-Selection enabled, the schema varies.

I will share an example here.

1. Patch to the Person or group field, which only allows single value.

The record of single person would contain the following values:

 

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Claims:"i:0#.f|membership|michael@wiXXXX.onmicrosoft.com",
    Department:"",
   DisplayName:"Michael Shao",
         Email:"Michael@wiXXXX.onmicrosoft.com",
      JobTitle:"",
       Picture:""
   }

Each value should match the pre-defined value stored under SharePoint data source, if you have no idea for the Department, JobTitle or Picture field, you may just leave it as "".

 

 

Fields need to be entered:

The Value for this field is fixed.

'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",

for Claims field,you should modify the end of this field to match the person Email:

Claims:"i:0#.f|membership|michael@wiXXXX.onmicrosoft.com",

And the DisplayName and Email field, as shown below:

 

 DisplayName:"Michael Shao",
         Email:"Michael@wiXXXX.onmicrosoft.com",

 

To patch a person to the Person or group field as a new record, the formula should be(Title is a required field when creating new records, so whenever a new record is created, all the required field should be get involved in the patch 3rd parameter.):

 

Patch(Patchtesting,
Defaults(Patchtesting), { Title:"SinglePerson", Person: {'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims:"i:0#.f|membership|michael@testing.com", Department:"", DisplayName:"Michael Shao", Email:"Michael@testing.com", JobTitle:"", Picture:"" }})

 

For Person or group Field which have Multiple selection enabled, the structure is a little difference.

For example, the following code would work to patch the MultValue person field:

Patch(Patchtesting,Defaults(Patchtesting),
{ Title:"MultiPerson",
Multi_x002d_Person: Table( { Claims:"i:0#.f|membership|michael@testing.com", Department:"IT", DisplayName:"Michael Shao", Email:"Michael@testing.com", JobTitle:"", Picture:""}, { Claims:"i:0#.f|membership|test2@testing.com", Department:"", DisplayName:"Test2", Email:"Test2@testing.com", JobTitle:"", Picture:""}) } )

Image reference:

47.PNG

48.PNG

46.PNG

 

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

@v-micsh-msft

Do you happen to know how to clear the Person column?

This code below doesn't work (while a similar code works for a regular lookup):

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Claims:"",
    Department:"",
   DisplayName:"",
         Email:"",
      JobTitle:"",
       Picture:""
   }

 

Anonymous
Not applicable

Bloodoff, did you end up getting this to work. i am after a similar result where i want to use the selected user details and patch them over.

Anonymous
Not applicable

@Anonymous nope, it's a limitation currently but there is an "idea" that covers both numeric and person fields. Please make sure to upvote it.

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Allow-us-to-update-a-numeric-field-to-null-blank-value/idi-p/11700

 

Anonymous
Not applicable

thanks, i dont suppose you know how to patch the selected user in a drop down.

 

I have

Column: {'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
                       Claims:"i:0#.f|membership|XXXX@XXXX.com",
                   Department:"",
                  DisplayName:"XXXX",
                        Email:"XXXX@XXXXX.com",
                     JobTitle:"",
                      Picture:""

 

where X = selected value. Ive tried user() and "" but no luck.

Anonymous
Not applicable

It is supposed to work and I have it working just fine. Make sure every bracket is in a proper place.

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims:"i:0#.f|membership|flast@contoso.com",
Department:"",
DisplayName:"First Last",
Email:"flast@contoso.com",
JobTitle:"",
Picture:""}

 

I have an app where this code works too:

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",Claims:Concatenate("i:0#.f|membership|",Office365Users.Manager(Email.Email).Mail),Department:"",DisplayNameffice365Users.Manager(Email.Email).DisplayName, Emailffice365Users.Manager(Email.Email).Mail, JobTitle:"", Picture:""}

 

@v-micsh-msft

 

I have been struggling with this for a couple of days.  For some reason, when I go to Patch, the column name (Employee_x0020_Name)  is not available.  

My DataCard is DataCard4, the property name is DataCardValue3.

Can you please tell me what I'm missing here?  

 

Thank you!

 

Patch(AppAdmins, Defaults(AppAdmins),
{Trying to put column name here:  
{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
Claims:"i:0#.f|membership|" & Lower(User().Email),
Department:"",
DisplayName: DataCardValue3.Selected.DisplayName,
Email:  DataCardValue3.Selected.Email,
JobTitle:".",
Picture:"."}});

Anonymous
Not applicable

hiya make sure you include the title in the first field of patching ie Title:titledatacard1.Text,

 

what do you have in {Trying to put column name here:  ?

 

also you need to specify all the metadata of the emails ie Employee Name:{Claims: dcvemployeename.Selected.Claims, Department: dcvemployeename.Selected.Department, DisplayName: dcvemployeename.Selected.DisplayName, Email: dcvemployeename.Selected.Email, JobTitle: dcvemployeename.Selected.JobTitle, Picture: dcvemployeename.Selected.Picture, '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser"

JeremyDIV
Advocate III
Advocate III

Does anyone else find this ridiculously complicated and counterintuitive for what should be a simple task?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (1,928)