cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JohnNash
Frequent Visitor

Updating information using multiple forms and the Patch function

Hi - 

 

I've been struggling for the last few days trying to figure out what I'm doing wrong.  

 

I have a Canvas app connected to a Sharepoint List called 'Vendor SetUp'.  It has 3 screens set up with forms to edit the data in the list and I've set up a button to send the updates to the list.  I found the below code in another post here and customized it to the app I'm working on but it doesn't update the information.

 

Patch('Vendor SetUp','Edit Vendor (V) Set Up Form - General Info'.Updates,'Edit Vendor (V) Set Up Form - Additional Info'.Updates,'Edit Temporary Activation Reason Form'.Updates)

 

Any ideas what I'm doing wrong?  

 

Thanks in advance,

 

John

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi@JohnNash,

Based on the issue that you mentioned, you mean that the 'Edit Vendor' is the primary key in the SP list. You want to refer to this unique value instead of ID in the SharePoint. 

Could you please share more about the 'Edit Vendor' column, is it a simple Text type or other else?

If my assumption is correct, you can modify the formula as below

 

Patch('Vendor SetUp',LookUp('Vendor SetUp','Edit Vendor'=DataCardValue6.Text),Form1.Updates,Form2.Updates)

 

If  'Edit Vendor' is a Choice column, please modify the formula as below

 

Patch('Vendor SetUp',LookUp('Vendor SetUp','Edit Vendor'=DataCardValue6.Selected.Value),Form1.Updates,Form2.Updates)

 

Note: DataCardValue6 is a control corresponding to 'Edit Vendor'.

002.png

Best Regards,

Qi

Best Regards,
Qi

View solution in original post

9 REPLIES 9
Pstork1
Most Valuable Professional
Most Valuable Professional

The second parameter of a Patch() function should be either defaults(datasource) for creating a new record, or something like a Lookup() that identifies the existing record to be updated.  You've supplied the updates, but don't tell the system what record to update.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

It's to update a record. 

 

So I'm confused then.  I played a little with lookup but I'm not sure how to use it along with the Patch command?  Lookup()(Patch(listname(etc?)) or patch(lookup(listname.selected)etc?

 

 

Pstork1
Most Valuable Professional
Most Valuable Professional

Assume you have a selected Item being used to populate the forms.  The patch() to update the record would look something like this.

Patch(Datasource,Lookup(Datasource,ID = selectedItem.ID),form1.updates, form2.updates, form3.updates)


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
v-qiaqi-msft
Community Support
Community Support

Hi@JohnNash,

Do you want to update a record in an existing SharePoint list?

Let me explain the syntax in Patch() at first. You can see the standard formula as below, if you want to update an existing record, you need to find out this record and that’s what the BaseRecord means.

 

Patch( DataSource, BaseRecord, ChangeRecord1 [, ChangeRecord2, … ] )

 

The formula you provided earlier doesn’t have a BaseRecord which allows you to create a new record by default. Actually, we are used to nesting Lookup() into a Patch() to update existing data. Using the Lookup function to compare the ID(or other primary keys in your list) of the records will be the key.

Thanks for the formula @Pstork1 provided, which will solve your updating issue.

Please modify your formula as below:

 

Patch('Vendor SetUp',Lookup(‘Vendor SetUp',ID=ThisItem.ID),'Edit Vendor (V) Set Up Form - General Info'.Updates,'Edit Vendor (V) Set Up Form - Additional Info'.Updates,'Edit Temporary Activation Reason Form'.Updates)

 

Best Regards,

Qi

Best Regards,
Qi

Hi QI and PStork1,

 

I modified the formula and this is the result:

 

It didn't come across in the clip, but it's highlighting ID=ThisItem.ID as the problem.

 

Annotation 2020-06-10 085609.png

Pstork1
Most Valuable Professional
Most Valuable Professional

The use of ID and Thisitem.ID was just an example.  You need to use a field from your datasource that can identify a specific record in the datasource.  Also the thisitem assumes you are on a form.  You may need to specify the target value differently.  The point is that it should be a logical operation that Identifies the record you want to update.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Hi@JohnNash,

 

Considering your confusion, let me make it easy for you. In general, each data source has a primary key for easy updating, and this primary key can be any column that is unique and does not duplicate. I reference ThisItem.ID because it is the primary key in the SharePoint list by default.

 

Take a simple example, if the record you want to update is the fifth row, then the ID of this record is 5, and you can just quote it as such, ID=5. The point is that you need to find the specific ID that corresponds to the record you need to update!

 

Best Regards,

Qi

Best Regards,
Qi

I get the concept and figured out the lookup but the patching function doesn't seem to like it.. it'd be really nice if there was some error output.

 

So I was able to match using this string which is the vendor's name: Patch('Vendor SetUp',LookUp('Vendor SetUp',Name='Edit Vendor'.Name),Form1.Updates,Form2.Updates) but even then the updates are not applied.  

 

(Note the fields are different this time around, I decided to rebuild the form off an example I found.)

 

But not on this, Vendor Setup.ID is the ID column from the SharePoint list the app is connected to and the 'Edit Vendor',ID is the corresponding field in the form itself.  I've verified the value is actually correct and the field is on the form but it's expecting a Record value?  I found some references that I'll need to convert the item to a number, I assume that's the number from the sharepoint list?  (I will continue to play)

 

Annotation 2020-06-11 131518.png

 

thanks for bearing with me.

 

Hi@JohnNash,

Based on the issue that you mentioned, you mean that the 'Edit Vendor' is the primary key in the SP list. You want to refer to this unique value instead of ID in the SharePoint. 

Could you please share more about the 'Edit Vendor' column, is it a simple Text type or other else?

If my assumption is correct, you can modify the formula as below

 

Patch('Vendor SetUp',LookUp('Vendor SetUp','Edit Vendor'=DataCardValue6.Text),Form1.Updates,Form2.Updates)

 

If  'Edit Vendor' is a Choice column, please modify the formula as below

 

Patch('Vendor SetUp',LookUp('Vendor SetUp','Edit Vendor'=DataCardValue6.Selected.Value),Form1.Updates,Form2.Updates)

 

Note: DataCardValue6 is a control corresponding to 'Edit Vendor'.

002.png

Best Regards,

Qi

Best Regards,
Qi

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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 (4,608)