Hi,
I am trying to create a very simple PowerApp based on a SharePoint list. This list has a Person field. When I initially create the PowerApp, if the user types in a person's name and chooses one, it saves fine. As soon as I try to default the Person field in the PowerApp to "current user" (using any of the User(). syntax options), my PowerApp stops saving back to the SharePoint source list.
Any ideas?
Solved! Go to Solution.
Thank you! this is exactly what I needed.
In here what is this SalesPerson_DD (in red text color)?
If( Account_Detail_Edit_Display_Long_1.Mode = FormMode.New,
{
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims:"i:0#.f|membership|" & Lower(User().Email),
Department:"",
DisplayName:User().Email,
Email:User().Email,
JobTitle:"",
Picture:""
}, SalesPerson_DD.Selected)
I am looking for the Same. Is there any updates now?
RebeccaS (somewhere in this thread) helped me - I'm copying it below:
If I want the data card to default to the current user I set a variable at the start that is = Set(_CurrentUser, User())
Then on the combo box I put as the DefaultSelectedItems: {DisplayName: _CurrentUser.FullName}
^ this does nothing but show the name so if you are hiding it then it is no necessary
Then on the cards Update value I put :
If(ComboBox.Selected.DisplayName=_CurrentUser.FullName,
{DisplayName: _CurrentUser.FullName,
Claims:"i:0#.f|membership|" & Lower(_CurrentUser.Email),
Department:"",
Email: _CurrentUser.Email,
JobTitle:"",
Picture:""}, ComboBox.Selected)
This is basically saying to default to the current user but if they change it then take that instead. I have seen several people say "easier" ways of doing it but I have been using this for a while and it works great...the other ways I have seen I have had trouble with them. This works 100% of the time for me.
If(DataCardValue2.Selected.DisplayName = strCurrentUser.FullName,{DisplayName: strCurrentUser.FullName, Claims:"i:0#.f|membership|" & Lower(strCurrentUser.Email),
Department:"",
Email: strCurrentUser.Email,
JobTitle:"",
Picture:""}, DataCardValue2.Selected)
I would just change the line of DisplayName: User().Email to DisplayName: User().FullName.
For people still viewing this thread, unless I'm misunderstanding how the sharepoint people backend works, you actually only need the claims field to be populated, as sharepoint will automagically derive all the other properties from it.
This means (according to my quick tests) the only line you need is
{Claims:"i:0#.f|membership|" & Lower(_CurrentUser.Email)}
Or, if you don't want to use a variable to store the current user (I wonder what the performance implications are with this, if any)
{Claims:"i:0#.f|membership|" & Lower(User().Email)}
If you need to populate a People column in SharePoint using a Power Automate flow, you're right: Claims (user's e-mail) is all you need. But when it comes to populating this column using a Power Apps app, it doesn't work because Power Apps identifies the register schema to save values to this column. When you add only Claims in a Patch, for example, red lines indicates you have an error and this error says the data source need a Record value, but with a different schema.
(translation of the image above, something like: "Invalid argument type. Waiting for a Record, but with a different schema. Missing column. Your formula has a missing column 'Department' with 'Text' type. Patch function has some invalid arguments")
So, reforcing some of the right answers to this question, the right schema is:
{
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims:"i:0#.f|membership|" & Lower(User().Email),
Department:"",
DisplayName:User().FullName,
Email:User().Email,
JobTitle:"",
Picture:""
}
While the patch function may fail without extra content, the Update function of a Data Card in a form seems to be just fine with just the claims.
I wonder, would the patch function work with empty values for every column, except claims ?
You're right, it works in Update property of the DataCard.
I also tested Patch function leaving all properties but Claims as blank values and it worked. So, you're right again. Claims is all you need, but using Patch function, the schema must be respected, even if you leave all other properties blank.
Just to add, for anyone that may have an issue when the people picker accepts multiple people. You need to enclose the object in a Table function
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!
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
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.
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