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

Patch just the fields that has changed

I need to Patch my Sharepoint List based on 50+ text/radio/dropdown inputs in my canvas app. Because there may be more than one user simultaneously changing the same record, I want to only Patch the fields that the user actually changed.

 

First, I tried to keep a single Record variable "varModifiedValues" to keep track of modified changes.

For every user input, I have something like this inside OnChange -

 

// Field A Text Input OnChange
Set(varModifiedValues,
  First( // get first record in the temp table
    AddColumns(
      DropColumns( // drop the column first so that it doesn't error out with 'column already exists'
        Table(varModifiedValues), // create temp table from the record variable
        "FieldA" // column to drop
      ),
      "FieldA",
      Self.Text
    )
  )
);

 

 This variable is a Record with only modified fields.

 

In the Save function, I tried to do this -

 

// Patch existing row; currSystemID is a variable that holds the ID of this row
Patch(System, LookUp(System, ID=currSystemID), varModifiedValues);

 

 

But this causes red squiggly line on Patch, saying "The specified column 'FieldA' does not exist. The column with the most similar name is 'FieldA'"

 

I've read in couple of places that using a variable to do a Patch may be problematic.

 

I can bite the bullet and do a Patch by specifying every field one by one for my 50+ inputs, but then I don't know how to NOT include the ones that did not change.

 

//assuming FieldA changed but FieldB didn't;

Patch(System, LookUp(System, ID=currSystemID),
  {
    'FieldA': varModifiedValues.FieldA, // this is ok
    'FieldB': varModifiedValues.FieldB // but this will overwrite FieldB with empty value because FieldB was never changed
  }

 

 

Is there a way to do something like 

 

Patch...
  {
   If(!IsBlank(varModifiedValues.FieldA), 'FieldA': varModifiedValues.FieldA) //only patch if value changed
  }

 

 

Or even better approach than what I have?

Hopefully I've explained my issue well enough. Thank you in advance.

1 ACCEPTED SOLUTION

Accepted Solutions

@at711 

 

You need to check Blank first 🙂

 

 

Patch(System, LookUp(System, ID=currSystemID),

{
FieldA:If(IsBlank(varModifiedValues.FieldA) || Lookup(System, ID = currSystemID, FiledA) = varModifiedValues.FieldA,Lookup(System, ID = currSystemID, FiledA), varModifiedValues.FieldA)
}

)

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

View solution in original post

5 REPLIES 5
SebS
Super User
Super User

@at711 

 

You can do something like this:

 

Patch(System, LookUp(System, ID=currSystemID),

{
FieldA:If(Lookup(System, ID = currSystemID, FiledA) = varModifiedValues.FieldA,Lookup(System, ID = currSystemID, FiledA), varModifiedValues.FieldA)
}

)

 

So this will look into the data source and pull this Field to Match it with the variable. If both are Blank, then they will stay blank, but if one of them is a different Variable will overwrite it. It will cost your performance but it should work.

 

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Thank you for your response.

So I think your logic says - 

//if sharepoint list FieldA = varModifiedValues.FieldA, use the value in sharepoint list

// else use varModifiedValues.FieldA

 

If Sharepoint List FieldA already has a value "Hello World" and the user does not change FieldA in the app, wouldn't it update Field A to blank, since varModifiedValues.FieldA is blank and it is different from SP list FieldA?

@at711 

 

Sorry Yes You are right forgot abut this one 🙂

 

 

Patch(System, LookUp(System, ID=currSystemID),

{
FieldA:If(Lookup(System, ID = currSystemID, FiledA) = varModifiedValues.FieldA || IsBlank(varModifiedValues.FieldA),Lookup(System, ID = currSystemID, FiledA), varModifiedValues.FieldA)
}

)

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

@at711 

 

You need to check Blank first 🙂

 

 

Patch(System, LookUp(System, ID=currSystemID),

{
FieldA:If(IsBlank(varModifiedValues.FieldA) || Lookup(System, ID = currSystemID, FiledA) = varModifiedValues.FieldA,Lookup(System, ID = currSystemID, FiledA), varModifiedValues.FieldA)
}

)

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Thank you, that would seem to work, although as you said I'm concerned about the performance.

I am a little baffled that this is the only working way to Patch things in Power Apps.

This question also suggests that you cannot use any dynamic name with Patch - 
https://powerusers.microsoft.com/t5/Building-Power-Apps/Patching-to-a-SharePoint-list-column-without...

 

Hopefully Power Apps reaches the level of maturity to do things like this soon.

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