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

For all Patch, only updating one record (collection part lookup)

I'm building an estimating app where the user can select accessory colors before converting the estimate to a contract. I have it set up where parts display in a gallery from a collection that gets created when the page loads. I am doing it this way so that qty, part numbers, cost, customer cost are persevered while material name, part number, and color can be updated by selecting a specific color.

 

Right now, it is functioning when the user goes through the gallery and clicks save on each item. I would like one button to update all the records however I am striking out. My patch only updates one record. Any guidance would be greatly appreciated!

 

gallery screenshot.png

DropDown to reference color options:

Items: Distinct(Filter(ColMaterials, Category = ThisItem.Category).Color,Color)

Default: ThisItem.Color


Save button: 

ForAll(Gallery8.AllItems,Patch(OrderLines,First(Filter(OrderLines,OrderIDRef=varOrderID&&Material=ThisItem.Material)),{Material:LookUp(ColMaterials,Category=ThisItem.Category&&Color=colordropdown.Selected.Result,'Material Name'),Color:colordropdown.Selected.Result,'Part Number':"test"}))

2 ACCEPTED SOLUTIONS

Accepted Solutions

@william_nr3 

Yeah, first, your ForAll is backward - you're trying to use it as a For/Loop.  It's a table producing function.  When you use it like a for/loop, your performance will suffer.

 

Your Datasource in this case is the Gallery.  In your formula you are not making that the source and thus it is just referencing the first row.

 

Your formula should be this:

Patch(OrderLines,                
    ForAll(Gallery8.AllItems As _item,
        {cr1a5_id: _item.cr1a5_id,
         Material: _item.colordropdown.Selected.'Material Name',
         Color: _item.colordropdown.Selected.Result,
         'Part Number':"test"
        }
    )
)

 

Your colordropdown Items property should contain the data necessary for the Material or it should be coming from another source to avoid the Lookup you had - but I'm not clear on how you have that part of it.

The important part here is to include the ID primary key in your resultant table that you are submitting to Patch.  Patch will know what to do with it then.

_____________________________________________________________________________________
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

@william_nr3 

Very good!!

Except you have an issue in that formula.  

It should be:

Patch(OrderLines,
    ForAll(Gallery8.AllItems As _item,
        {cr1a5_id: _item.cr1a5_id,
       Material: _item.timat.Text,
         Color: _item.colordropdown.Selected.Result,
         'Part Number':"test"
        }
    )
)

Having the extra gallery table in the Patch like that will cause issues.

_____________________________________________________________________________________
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

7 REPLIES 7

@william_nr3 

What is your datasource you are using?

You should be working with the primary key of the data and also your ForAll is backward and being used as a For/Loop...which it's not.

Also you are referencing ThisItem...are you doing this in some control beside a button?

 

_____________________________________________________________________________________
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!

Hey Randy, thanks for the reply. I am using Dataverse as my data source for the gallery. I am using 'ThisItem' to reference the value that I want in the record.

@william_nr3 

Sorry, didn't notice that the save button was in the gallery!!

But here is the thing - if you have a save button in the row, then the implication is that you are saving that row.  So then why would you be saving the whole gallery?

 

_____________________________________________________________________________________
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!

You are totally right. I started small with saving each record so that's why I have a save in each row. I would like to save the whole gallery. I took your guidance and have a save button outside of the gallery now + referencing the primary key. It runs but updates all the records in the gallery with the Material Name, Color, and Part Number from the first row. I'm not sure what I am missing.

 

ForAll(RenameColumns(OrderLines,"cr1a5_id","Custom_ID"),Patch(OrderLines,LookUp(Gallery8.AllItems,cr1a5_id=Custom_ID),{Material:LookUp(ColMaterials,Category=TextInput9.Text&&Color=colordropdown.Selected.Result,'Material Name'),Color:colordropdown.Selected.Result,'Part Number':"test"}))

@william_nr3 

Yeah, first, your ForAll is backward - you're trying to use it as a For/Loop.  It's a table producing function.  When you use it like a for/loop, your performance will suffer.

 

Your Datasource in this case is the Gallery.  In your formula you are not making that the source and thus it is just referencing the first row.

 

Your formula should be this:

Patch(OrderLines,                
    ForAll(Gallery8.AllItems As _item,
        {cr1a5_id: _item.cr1a5_id,
         Material: _item.colordropdown.Selected.'Material Name',
         Color: _item.colordropdown.Selected.Result,
         'Part Number':"test"
        }
    )
)

 

Your colordropdown Items property should contain the data necessary for the Material or it should be coming from another source to avoid the Lookup you had - but I'm not clear on how you have that part of it.

The important part here is to include the ID primary key in your resultant table that you are submitting to Patch.  Patch will know what to do with it then.

_____________________________________________________________________________________
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!

Got it- thanks a ton. I got it working with the code below. I removed the lookup and put the lookup in the gallery itself (made it invisible). I may not be optimal, but the goal is for the user to change the color of the part and when they save it, it references the materials collection and updates the part in OrderLines with the appropriate name, color, and part number. The base quantity, customer price, and cost remain untouched. 

 

Patch(OrderLines, Gallery8.AllItems,
    ForAll(Gallery8.AllItems As _item,
        {cr1a5_id: _item.cr1a5_id,
       Material: _item.timat.Text,
         Color: _item.colordropdown.Selected.Result,
         'Part Number':"test"
        }
    )
)

@william_nr3 

Very good!!

Except you have an issue in that formula.  

It should be:

Patch(OrderLines,
    ForAll(Gallery8.AllItems As _item,
        {cr1a5_id: _item.cr1a5_id,
       Material: _item.timat.Text,
         Color: _item.colordropdown.Selected.Result,
         'Part Number':"test"
        }
    )
)

Having the extra gallery table in the Patch like that will cause issues.

_____________________________________________________________________________________
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!

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 (605)