Hello! I'm trying to get a patch function to work to recognize if a user has submitted the form before and if so, update preferences.
Backstory: App is a simple form for signing into a company event. A user walks up and selects their name in the people picker field of the form and there are checkboxes below that ask if they would like to receive email communications in the future. The first time works great. I have a flow that looks up their department and email and inserts into the destination SharePoint list.
When that same user goes to a future and wants to update their communication preferences I can't get it to see if the name selected in the people picker field exists so the record can be updated and not created new.
Currently, the below patch function creates a NEW record with a blank name in the SharePoint list.
Patch('LIst Name',{Name:DataCardValue6.Selected},{'Preferences One':DataCardValue7.Text,'Preference Two':DataCardValue8.Text,'Preference Three':DataCardValue11.Text})
Am I having issues because it's a People Picker?
To patch a people field into a SharePoint list you would use something like this:
Patch(SPList, Defaults(SPList),
{Title:"Whatever",
PPLField: {
DisplayName: ComboBox.Selected.DisplayName,
Claims: "i:0#.f|membership|" & Lower(Combobox.Selected.Email),
Department:"",
Email: ComboBox.Selected.Email,
JobTitle:"",
Picture:""}
}
)
I don't believe so. When I created the SharePoint list the column is a people picker and so I'm not sure it created a combo box when I connected the form to the SharePoint data source.
If you are using a Form (which I always think is the better route)...what is your Patch doing? I am not understanding this part.
Hi @mlaurie .
Actually you do not need to add such a separated person and group field. By default, in SharePoint list, there is one field called "Author" which is created by SharePoint automatically when user submitting one item. You could check if current user exists in this field. The formula should be something like:
If(IsBlank(Lookup(ListName,Author.Email=User().Email)),Patch(ListName,Defaults(ListName),{Title:textinput1.Text,
PersonField:Dropdown.Selected}),
Patch(ListName,Lookup(ListName,Author.Email=User().Email),
{Title:textinput1.Text,
PersonField:Dropdown.Selected}))
This formula means that if current user is not included in the Author field, then create a new item. If current user already exists in the Author field, then edit this item.
If you are using the Form control, then for Patch function, you just need to copy and paste the formulas in the Update property of each data card for each field.
Regards,
Mona
I'd like the patch to update the user's communication preferences if the name selected in the form matches a name that exists in the SharePoint list.
Will this work if I'm the one who opens the app and my "customers" come and sign in by selecting their name?
@v-monli-msft wrote:Hi @mlaurie .
Actually you do not need to add such a separated person and group field. By default, in SharePoint list, there is one field called "Author" which is created by SharePoint automatically when user submitting one item. You could check if current user exists in this field. The formula should be something like:
If(IsBlank(Lookup(ListName,Author.Email=User().Email)),Patch(ListName,Defaults(ListName),{Title:textinput1.Text,
PersonField:Dropdown.Selected}),
Patch(ListName,Lookup(ListName,Author.Email=User().Email),
{Title:textinput1.Text,
PersonField:Dropdown.Selected}))
This formula means that if the current user is not included in the Author field, then create a new item. If the current user already exists in the Author field, then edit this item.
If you are using the Form control, then for Patch function, you just need to copy and paste the formulas in the Update property of each data card for each field.
Regards,
Mona
Hi @mlaurie ,
User().Email returns the current logged in PowerApps user's email address. So I don't understand what you mean by "my "customers" come and sign in".
If you share this app with a "customer", then he open the app from his PowerApps site. He will be the "current logged in user", and User().Email will become his PowerApps account email address in this app.
For more information about User function, please refer to:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-user
Regards,
Mona
The scenario is the following:
I login to PowerApps on a tablet device. People walk into the event I'm hosting and enter their name and preferences on the device that I am logged into. We want their preferences to be updated if their name is already in the list from attending an event in the past where we had them enter their name and preferences before.
Sorry for any confusion.
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