cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Patch doesn't work on same data source in a row

Hello, need some help:

 

See the code below:

Facts:

1.  They both do a change to two different records on the same data source.

2.  Both statements work independently 

 

Question: The first Patch works and the second one doesn't.  If I reverse the order of the patch statements then the first one works and the second one doesn't.  I can't get both Patch statements to work.  

 

Note:  This code operates when the user pushes a button

IMPORTANT:  This code does not cause an error.  It runs if the patches are in either order, but it is only updating the data source 1 time, with the update that is in the first path.

 

Thank you!!!

 

//Update date of last status change
Patch(
FeeRequestTracking,
Last(
Filter(
FeeRequestTracking,
RequestID = RequestGallery.Selected.ID && 'End Status' = StartStatus
)
),
{EndStatusChanged: Now()}
);

//Update tracking information
Patch(
FeeRequestTracking,
Defaults(FeeRequestTracking),
{RequestID: RequestGallery.Selected.ID},
{'Begin Status': StartStatus},
{'End Status': EndStatus},
{ReviewerComments: txtReviewerComments.HtmlText}//Store comment in original Fee Request and in Tracking. Future updates should be recorded in FeeRequestTracking.
);

2 ACCEPTED SOLUTIONS

Accepted Solutions

Hi @subsguts ,

Hidden button or icon would both work, although it makes no sense to me why it does not work in the first place. Place a Notify at the end of your original code as below (this is only a debugging exercise) and see if you get a message with the ID of the new record (or any message).

With(
   {
      wID:
      LookUp(
         Sort(
            FeeRequestTracking,
            ID,
            Descending
         ),
         RequestID = RequestGallery.Selected.ID && 
         'End Status' = StartStatus
      ).ID
   },
   Patch(
      FeeRequestTracking,
      {ID: wID},
      {EndStatusChanged: Now()}
   )
);
Set(
   gblTestID,
   Patch(
      FeeRequestTracking,
      Defaults(FeeRequestTracking),
      {
         RequestID: RequestGallery.Selected.ID,
         'Begin Status': StartStatus,
         'End Status': EndStatus,
         ReviewerComments: txtReviewerComments.HtmlText
      }
   ).ID
);
Notify(
   "Your Patched ID is " & gblTestID,
   Success
)

 

View solution in original post

@subsguts ,

OK - if it gave an ID, there should be a record there. Have you refreshed SharePoint (directly in SharePoint), created a view sorted by ID descending and see if the record is there ?

View solution in original post

10 REPLIES 10
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @subsguts ,

Other than being more specific on the update, it should work

With(
   {
      wID:
      LookUp(
         Sort(
            FeeRequestTracking,
            ID,
            Descending
         ),
         RequestID = RequestGallery.Selected.ID && 
         'End Status' = StartStatus
      ).ID
   },
   Patch(
      FeeRequestTracking,
      {ID: wID},
      {EndStatusChanged: Now()}
   )
);
Patch(
   FeeRequestTracking,
   Defaults(FeeRequestTracking),
   {
      RequestID: RequestGallery.Selected.ID,
      'Begin Status': StartStatus,
      'End Status': EndStatus,
      ReviewerComments: txtReviewerComments.HtmlText
   }
);

You also should do the update first to ensure the new record just written does not become the update.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

 

Thanks for your reply.

 

Unfortunately, this code change, like the original only executes the first Patch.  The new record is never created and only the update is performed.

If you have any other suggestions that would be great!

The only way I've been able to get this to work (albeit a kludge in my opinion), is to take the Patch that does the update and move it to a button.  Then I do a Select(button).  I do grab the ID needed.  Here is the kludgy code in case it helps you suggest another way to make it work in the same place, which I would greatly appreciated as this below is definitely not "good programming".

Change to Code in original button pressed by the user:

Set(varTrackID,Last(Filter(FeeRequestTracking,RequestID=RequestGallery.Selected.ID && 'End Status'=StartStatus)).ID);

Select(btnUpdatesFeeTrackingDate);


//Update tracking information
Patch(
FeeRequestTracking,
Defaults(FeeRequestTracking),
{RequestID: RequestGallery.Selected.ID},
{'Begin Status': StartStatus},
{'End Status': EndStatus},
{ReviewerComments: txtReviewerComments.HtmlText}//Store comment in original Fee Request and in Tracking. Future updates should be recorded in FeeRequestTracking.
);

 

Button OnSelect Code:

//Update tracking information by adding the EndStatusChagne timestamp on the last change of status before the current one
Patch(
FeeRequestTracking,
{ID:varTrackID},
{EndStatusChanged: Now()}
);

 

Hi @subsguts ,

Hidden button or icon would both work, although it makes no sense to me why it does not work in the first place. Place a Notify at the end of your original code as below (this is only a debugging exercise) and see if you get a message with the ID of the new record (or any message).

With(
   {
      wID:
      LookUp(
         Sort(
            FeeRequestTracking,
            ID,
            Descending
         ),
         RequestID = RequestGallery.Selected.ID && 
         'End Status' = StartStatus
      ).ID
   },
   Patch(
      FeeRequestTracking,
      {ID: wID},
      {EndStatusChanged: Now()}
   )
);
Set(
   gblTestID,
   Patch(
      FeeRequestTracking,
      Defaults(FeeRequestTracking),
      {
         RequestID: RequestGallery.Selected.ID,
         'Begin Status': StartStatus,
         'End Status': EndStatus,
         ReviewerComments: txtReviewerComments.HtmlText
      }
   ).ID
);
Notify(
   "Your Patched ID is " & gblTestID,
   Success
)

 

Thanks, I will try this and let you know.

 

BTW, the btn worked for a while and now has stopped.  I am totally 100% CONFUSED as it makes no sense why this functionality doesn't work.  It's almost like it needs time to process the one patch before it does the second and that it gets confused hitting the same SP list at the same time and doesn't like that.

 

Anyway, I'll try to debug with what you've sent and see if that leads to any solutions and report back my finding.

 

I tried it.  It did give me a message with an ID in it.  However, it did not created the new record. 

I think this has to be a timing issue.  

 

The reason I think this is because if I take one of the Patch statements out and put it on a button and manually push it after this code runs it works.  It's like I need some time in between the two patch statements.

 

Any thoughts with this additional info? 

 

Thanks for sticking with me on this... I think this is a tough one and maybe a PowerApps Bug.

Just to retest, I commented out the first patch as follows and it DOES create the new record.  So something in the first one is keeping the second from successfully creating the record... as strange as this is and makes no sense to me.

 

Any ideas?

 

/*
With(
{
wID:
LookUp(
Sort(
FeeRequestTracking,
ID,
Descending
),
RequestID = RequestGallery.Selected.ID &&
'End Status' = StartStatus
).ID
},
Patch(
FeeRequestTracking,
{ID: wID},
{EndStatusChanged: Now()}
)
);*/
Set(
gblTestID,
Patch(
FeeRequestTracking,
Defaults(FeeRequestTracking),
{
RequestID: RequestGallery.Selected.ID,
'Begin Status': StartStatus,
'End Status': EndStatus,
ReviewerComments: txtReviewerComments.HtmlText
}
).ID
);
Notify(
"Your Patched ID is " & gblTestID,
Success
);

@subsguts ,

OK - if it gave an ID, there should be a record there. Have you refreshed SharePoint (directly in SharePoint), created a view sorted by ID descending and see if the record is there ?

Thanks for the pointer.  Using your logic, I put in a Lookup after the store of the record and got a the record id in the table.  When I went to that record the RequestID field was blank.  I expected that to be populated, so somehow that field is getting cleared.  I'm working through this, but brain is fried.  So will attempt again in the morning.   You've been a BIG Help.  While I don't have the solution, I'm marking this as solved as not it appears to not be PATCH issue, but more with the data being passed issue, which is something only I can solve.

 

I will post an update on this though to either confirm or deny that the two patch statements can work side by side.

 

The best part of this solution for folks reading is the Debugging part.  I didn't know about this and it is really very very valuable.  

 

Thanks!!!

Just to close this out.  The issue was that a the RequestGallerySelected.ID was become blank due to some refreshes of the gallery that were happening as other variable were also change that affected it's display.  Therefore the solution was to store this in a variable and use it instead of referencing the Gallery directly.  I know it's a best practice by some to store this in the OnSelect of the Gallery.  So this is one place where that would have eliminated this issue.  Thanks again for the help.

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

Top Solution Authors
Top Kudoed Authors
Users online (1,850)