Hi,
I'm looking for an example on how I can access the returned value from a patch function.
The reference here: Here advises
"The return value of Patch is the record that you modified or created. If you created a record, the return value may include properties that the data source generated automatically."
But how do i access this value?
Example, I am using SharePoint as a datasource.
I'm creating a new list item using the formula below.
Patch(SharePointList,Defaults(SharePointList),{Title:"Test",Blah:1234})
When an item is created in SharePoint it is given an auto-generated ID. I'm looking to access the returned value/record so I can use the given ID within my app without having to re-query the datasource.
Can anyone provide an example on how this can be acheived?
Thanks.
Solved! Go to Solution.
Hi @duffysp
The documentation is pretty poor in the way it explains it.
You need to do this:
ClearCollect(MyPatchedRecords, Patch(SharePointList,Defaults(SharePointList),{Title:"Test",Blah:1234}))
MyPatchedRecords will contain one record in case of a single record patch, or multiple records if the patch statement patches a set of records.
You can also use the above for the Remove/RemoveIf function; but rather oddly the PowerApps team have decided to return not the deleted record/records but all the remaining records of the data source after the Remove/RemoveIf. However, due to delegation issues, only 500 records will be returned, so this is useless for medium/large data sources
Hi @duffysp
The documentation is pretty poor in the way it explains it.
You need to do this:
ClearCollect(MyPatchedRecords, Patch(SharePointList,Defaults(SharePointList),{Title:"Test",Blah:1234}))
MyPatchedRecords will contain one record in case of a single record patch, or multiple records if the patch statement patches a set of records.
You can also use the above for the Remove/RemoveIf function; but rather oddly the PowerApps team have decided to return not the deleted record/records but all the remaining records of the data source after the Remove/RemoveIf. However, due to delegation issues, only 500 records will be returned, so this is useless for medium/large data sources
So... what happens if the patch function fails for some reason (e.g the connection to the database fails). How does PowerApps manage this and how do I access the error message that is returned?
Hi @FBGLUCK
Two things:
1) MyPatchedRecords in the above example will be empty
2) You can use the Errors() function to retrieve any errors, see the documentation for details
PowerApps may also give feedback in the browser, but that is not a process that you control.
Hope this helps.
Thanks so much @Meneghino, this was a real life-saver.
I don't think I would have realized how this was supposed to work without your answer so kudos to you!
can we get record Id which is created by Patch function here ? in Powerapps to set that id in another entity's lookup field by another patch statement ?
If you include the Defaults(DataSource) in your patch statement, it will return the ID in the collection.
So use this format (as noted above):
ClearCollect(MyPatchedRecords, Patch(SharePointList,Defaults(SharePointList),{Title:"Test",Blah:1234}))
Then you can access the collection to get your ID value. For example, my collection will only have one record so I will use First to get the record I want to pull the ID from.
This is the code I used to set varID with my newly patched record's ID:
UpdateContext({varID:First(MyPatchedRecords).ID})
Hi @Anonymous,
I need to utilize the ID immidiately after patching. The process is as follows:
- User fills in input and presses OK when finished
- The button "OK" patches to a SQL server and saves information in a collection like you described.
- Ideally, the press on OK also triggers a mail that sends a link that includes the ID to another user.
However, the values in the mail are empty - it seems like powerapps is too slow saving the information in the collection, so that the reference returns an empty value from the collection (I have checked the flow sending the email and the input is empty). I have tested to simply write the results from the collection in a textbox in my app and the values are shown here after patching - so I do not think my code is the problems.
Any idea/workaround to how I can manage to add this information to the mail immediatly after patching?
Alternatively, if you know you are going to patch a single record, consider using a context variable instead to capture the returned record and use that to get fields within the returned record. E.g.
UpdateContext({ReturnedRecord : Patch(SharePointList,Defaults(SharePointList),{Title:"Test",Blah:1234})});
// get SharePoint ID field within ReturnedRecord
Set(ResultID, ReturnedRecord.ID)
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