cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
lumberjacklurch
Responsive Resident
Responsive Resident

Patch SPO list using records in a collection

I have found a few posts similar, but none are an exact match for my issue.  I have a SPO request list, and an accompanying SPO list that lists the items for the request.  What I want to happen, is when a person opens an item in the request list, edits the item (in the customized form), and changes a text field, I want a column in the accompanying item list to relect the change in the request list.  Seems simple enough, but my problem lies in that there may be multiple records in the accompanying item list that point to a single record/item in the request list.  If someone were to change the record/item in the request list, how to I update all the corresponding records in the items list?  The only fields they have in common are the title and ID (the request list record's ID is saved to a 'Request ID' column in the item list).  I have tried the below, but it complains about getting a Table result instead of a Record.

 

ClearCollect(col_AllItems, SortByColumns('Item List', "ID", Ascending))

 

ClearCollect(col_ItemDetailEdit, ShowColumns(Filter(col_AllItems, var_SharepointSelectedID in 'Request ID'), "ItemName", "ItemDescription", "ItemQuantity","ID", "Title"))

 

ForAll(col_ItemDetailEdit, Patch('Item List', Filter('Item List', ID in col_ItemDetailEdit.ID), {Title: Title}))

1 ACCEPTED SOLUTION

Accepted Solutions

@lumberjacklurch 

No problem on the help...hang in there, it will all start to "click" eventually, and we'll get this problem solved also.

 

So, let's make some changes...It seems that we're getting some of what we need and the stage is set from the tests.

 

Let's change the Formula in the OnSave to this:

If(SharepointFormMode="CreateForm", 
   SubmitForm(FormNew), 
   SubmitForm(RequestFormEdit)
   );
 
If(SharepointFormMode="EditForm", 
   ForAll(RenameColumns(Filter('Item List', SharePointIntegration.SelectedListItemID in 'Request ID'), "ID", "fID"), 
          Patch('Item List', 
                LookUp('Item List', ID = fID), 
                {Title: RequestFormEdit.LastSubmit.Title
                }
                )
          )
   

The only real difference here is that we are pulling out the extra collection stage and simply running the ForAll against what would have been the same results as the collection.  Not sure if you actually need that collection some place else, but let's ignore that for the moment.

Just so I didn't think I was going crazy...I just tested this out with the same concepts that you are using - and all worked fine.

Let's see what happens for you next.

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

17 REPLIES 17

@lumberjacklurch 

 

You're most likely getting that error in your ForAll formula on the Patch function.  In your formula you are providing a table rather than a record (as the error suggests).

Consider changing your formula to the following:

ForAll(col_ItemDetailEdit, Patch('Item List', Lookup('Item List', ID = col_ItemDetailEdit.ID), {Title: Title}))

I hope that is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Thanks for the reply RandyHayes!

 

I got this to work for my Submit button:

 

ForAll(col_ItemDetailEdit, Patch('Item List', {ID: ID}, {Title: RequestFormEdit.LastSubmit.Title}))

 

It doesn't work in the SharePointIntegration OnSave though.  I know there are limitations on the SharePointIntegration properties.  Perhaps Patch is one of them?

@lumberjacklurch 

Although that will work, for the most part, I wouldn't recomend that syntax.  The formula I mentioned previously will be accurate all the time as it is getting the record (with the Lookup) that is intended to be Patched.

 

What problem are you running into in the OnSave?  The Patch function will work there as well, but perhaps you are running into some other issue.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

I tried the Lookup code you provided, but I get the red squiggly line under the equals sign, with the error: "Invalid argument type.".  

I changed the = to "in", and got rid of the error.  A problem with the Lookp though, Lookup only grabs one record, butg there is potential for more than one record needing processing.  That's why I wasn't using Lookup.  I tried Filter, but it gave me an error saying it was expecting a Record value and I was giving it a Table value.

@lumberjacklurch 

 

I tried the Lookup code you provided, but I get the red squiggly line under the equals sign, with the error: "Invalid argument type.".

Yes, you actually need to change your formula to this - sorry I was focused on the Lookup part rather than the comparison of ID.

 

ForAll(col_ItemDetailEdit, Patch('Item List', Lookup('Item List', ID = col_ItemDetailEdit[@ID]), {Title: Title}))

 

 

 

I changed the = to "in", and got rid of the error.  A problem with the Lookp though, Lookup only grabs one record, butg there is potential for more than one record needing processing.  That's why I wasn't using Lookup.  I tried Filter, but it gave me an error saying it was expecting a Record value and I was giving it a Table value.

This is why you are using a ForAll - to process all the items in the col_ItemDetailEdit collection.  This will loop through each one and issue the Patch function for each one.

Patch cannot have a table as a source for a record.  You need to supply what record you want to patch.  In this case, with a lookup.  You would not want that part to have multiple records - and, it's quite impossible to have multiple records with the same ID.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes 

I tried the last iteration, and it behaves the same as the code I mentioned earlier.  It worked for the Submit button, but not the OnSave property.  There must be some sort of restriction for that property.

@lumberjacklurch 

So, what does your formula look like now in the OnSave action?  

Are you getting any particular error or what is not happening?

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes 

 

Here's the code in the OnSave property:

 

If(SharepointFormMode="CreateForm", SubmitForm(FormNew), SubmitForm(RequestFormEdit));

 

ClearCollect(col_ItemDetailEdit, ShowColumns(Filter('Item List', SharePointIntegration.SelectedListItemID in 'Request ID'), "ItemName", "ItemDescription", "ItemQuantity","ID", "Title"));

 

If(SharepointFormMode="EditForm", ForAll(col_ItemDetailEdit, Patch('Item List', LookUp('Item List', ID = col_ItemDetailEdit[@ID]), {Title: RequestFormEdit.LastSubmit.Title})))

 

I get no errors, it just doesn't update the 'Item List' records.

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

Users online (664)