cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ez1138
Post Patron
Post Patron

Patch SQL, Want to Update an Record, Not Create a New One

Hi, using the following code I was aiming to update a record, not create a new one.  When I edit the record, let's say the first one (e.g. St. Louis, Company_ID 1), and I change it to Las Vegas, it creates a new record.  

 

What do I need to modify to simply update?  Also, what other code can I add in to return back to the detail/display screen for that record?

 

Thanks for any assistance!!

 

Patch('[dbo].[table1]', Defaults('[dbo].[table1]'), {City: DataCardValue318.Text})

 

2020-05-07_9-42-38.jpg

1 ACCEPTED SOLUTION

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @ez1138 ,

How do you collect your entry? Using Edit form or individual Text Input Boxes?

Do you want to submit data back to your SQL Table using Patch function instead of SubmitForm function?

Further, how do you list your SQL Table records in your app? Using Gallery control?

 

I assume that you use a Gallery control in your app to list all available records from your SQL Table, and you add a Edit form control to collect entry for adding or updating records in your SQL Table, right?

 

If you want to update an existing record in your SQL Table, I think the Patch formula you provided is wrong. The Defaults() function within the Patch function is used to add a new record in your SQL Table rather than update.

 

I have made a test on my side, please consider take a try with the following workaround:

I assume that you added a Edit form in your canvas app to add or edit records in your SQL Table, and the Item property of the Edit form has been bind to the selected item in your Gallery.

Set the Item property of the Edit form to following:

 

BrowseGallery1.Selected

 

set the DataSource property of the Edit form to your SQL Table data source ('[dbo].[table1]').

Set the OnSelect property of the "Submit" button in your Edit form screen to following:

 

Patch(
      '[dbo].[table1]',
      If(                     // Check if you are adding or editing record
          EditForm1.Mode = FormMode.New,
          Defaults('[dbo].[table1]'),        // Type this formula when adding record
          BrowserGallery1.Selected           // Find specific record you want to update when editing
      ),
      EditForm1.Updates
)

 

or

 

Patch(
      '[dbo].[table1]',
      If(                     // Check if you are adding or editing record
          EditForm1.Mode = FormMode.New,
          Defaults('[dbo].[table1]'),        // Type this formula when adding record
          LookUp('[dbo].[table1]', MyID = BrowserGallery1.Selected.MyID)       // Find specific record you want to update when editing
      ),
      EditForm1.Updates            // you could also type {City: DataCardValue318.Text} formula here
)

 

Note: The BrowserGallery1 represents the Gallery in your app to list all available records from your SQL Table. You could click the item in this Gallery to navigate to the Detail Screen, within the Detail Screen, you could click "Edit" icon to navigate to Edit form screen. The EditForm1 represents the Edit form in your Edit screen, please replace it with actual Edit form name

 

If you want to return back to the detail screen for that record you are updating after you execute the Patch function, please consider modify above Patch formula as below:

 

If(                     // Check if you are adding or editing record
    EditForm1.Mode = FormMode.New,
    Patch(
         '[dbo].[table1]',
          Defaults('[dbo].[table1]'),
          EditForm1.Updates
    );Navigate(GalleryScreen),
     Patch(
         '[dbo].[table1]',
          BrowseGallery1.Selected, // or type LookUp('[dbo].[table1]', MyID = BrowserGallery1.Selected.MyID) here
          EditForm1.Updates   // you could also type {City: DataCardValue318.Text} formula here
    );Navigate(DetailScreen)
)
    

 

Note: The GalleryScreen represents the first screen in your app.

 

Please take a try with above solution, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
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

10 REPLIES 10

@ez1138 

To update the record with ID=1 use this code. 

 

Patch('[dbo].[table1]', LookUp('[dbo].[table1]', ID=1), {City: DataCardValue318.Text})

 

If you want to get back the full information about the record you updated store it in a SET variable

 

Set(updatedRecord, Patch('[dbo].[table1]', LookUp('[dbo].[table1]', ID=1), {City: DataCardValue318.Text}))

 

Then you can refer to any column in the updatedRecord like this (place it in a label Text property)

 

updatedRecord.City

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up." 

Appreciate the reply.  I will try it out.  Quick follow-up.  You have ID=1.  Isn't that specific to that one record?  I might choose any record to update.

 

Set(updatedRecord, Patch('[dbo].[table1]', LookUp('[dbo].[table1]', ID=1), {City: DataCardValue318.Text}))

 

@ez1138 
Yes, I chose ID=1 because your example asked for record number 1 lol 😉

You can dynamically change the record to be updated by referring to a variable (varCurrentId)

Set(updatedRecord, Patch('[dbo].[table1]', LookUp('[dbo].[table1]', ID=varCurrentId), {City: DataCardValue318.Text}))

 

Or if your update button is inside a form or gallery you can refer to ThisItem.ID instead.

Set(updatedRecord, Patch('[dbo].[table1]', LookUp('[dbo].[table1]', ID=ThisItem.ID), {City: DataCardValue318.Text}))

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

LOL, yeah, not the first time I asked for the wrong thing!  With both pieces of code, it doesn't seem to like the ID...it seems to like everything else.

 

2020-05-07_10-17-30.jpg

@ez1138 
You have to create a variable to store the ID.  I just put a sample variable name in my code.  Its not going to work unless you create a variable.

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Hi, now I'm confused some more.  In my table I have the following:

 

MyID (Primary Key)

Company_ID (references Company Table)

Contact_ID (references Contacts Table)

 

Regarding a variable, I'm not sure what you mean.  I have not seen variable used in other patch examples.

@ez1138 
What I mean is store the value 1 in a variable.  Then call the variable instead of the number.

 

Set(varCurrentID, 1);

 

 

The question for you is: how are you choosing which record will be updated?

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

v-xida-msft
Community Support
Community Support

Hi @ez1138 ,

How do you collect your entry? Using Edit form or individual Text Input Boxes?

Do you want to submit data back to your SQL Table using Patch function instead of SubmitForm function?

Further, how do you list your SQL Table records in your app? Using Gallery control?

 

I assume that you use a Gallery control in your app to list all available records from your SQL Table, and you add a Edit form control to collect entry for adding or updating records in your SQL Table, right?

 

If you want to update an existing record in your SQL Table, I think the Patch formula you provided is wrong. The Defaults() function within the Patch function is used to add a new record in your SQL Table rather than update.

 

I have made a test on my side, please consider take a try with the following workaround:

I assume that you added a Edit form in your canvas app to add or edit records in your SQL Table, and the Item property of the Edit form has been bind to the selected item in your Gallery.

Set the Item property of the Edit form to following:

 

BrowseGallery1.Selected

 

set the DataSource property of the Edit form to your SQL Table data source ('[dbo].[table1]').

Set the OnSelect property of the "Submit" button in your Edit form screen to following:

 

Patch(
      '[dbo].[table1]',
      If(                     // Check if you are adding or editing record
          EditForm1.Mode = FormMode.New,
          Defaults('[dbo].[table1]'),        // Type this formula when adding record
          BrowserGallery1.Selected           // Find specific record you want to update when editing
      ),
      EditForm1.Updates
)

 

or

 

Patch(
      '[dbo].[table1]',
      If(                     // Check if you are adding or editing record
          EditForm1.Mode = FormMode.New,
          Defaults('[dbo].[table1]'),        // Type this formula when adding record
          LookUp('[dbo].[table1]', MyID = BrowserGallery1.Selected.MyID)       // Find specific record you want to update when editing
      ),
      EditForm1.Updates            // you could also type {City: DataCardValue318.Text} formula here
)

 

Note: The BrowserGallery1 represents the Gallery in your app to list all available records from your SQL Table. You could click the item in this Gallery to navigate to the Detail Screen, within the Detail Screen, you could click "Edit" icon to navigate to Edit form screen. The EditForm1 represents the Edit form in your Edit screen, please replace it with actual Edit form name

 

If you want to return back to the detail screen for that record you are updating after you execute the Patch function, please consider modify above Patch formula as below:

 

If(                     // Check if you are adding or editing record
    EditForm1.Mode = FormMode.New,
    Patch(
         '[dbo].[table1]',
          Defaults('[dbo].[table1]'),
          EditForm1.Updates
    );Navigate(GalleryScreen),
     Patch(
         '[dbo].[table1]',
          BrowseGallery1.Selected, // or type LookUp('[dbo].[table1]', MyID = BrowserGallery1.Selected.MyID) here
          EditForm1.Updates   // you could also type {City: DataCardValue318.Text} formula here
    );Navigate(DetailScreen)
)
    

 

Note: The GalleryScreen represents the first screen in your app.

 

Please take a try with above solution, check if the issue is solved.

 

Best regards,

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

Thank you so, so much! This worked great and I appreciate the extra time and depth for your post!  If you wouldn't mind, I will PM you down the line.  Again, many thanks!

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