cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
FrankKelp
Helper I
Helper I

Patching a collection using a ForAll() Function

Hi all, 

 

Hoping someone can point me in the right direction here with a small issue regarding patching an entire collection to Dataverse. 

 

I have a multi select gallery were the user can select more than one item. As such I am attempting to patch an entire collection to a dataverse table. 

 

The issue I am having is with my second ForAll() that performs the actual patch. 

 

I collect all items in the gallery in the first ForAll(), but when I patch to the datasource, what I end up with is three duplicate values. 

 

For context, my testing was performed with 3 records in the collection, but instead of creating three unque rows, I get 3 duplicate rows of the first record in the collection. Hope that makes sense. 

 

Has anyone ran into the same issue before, if so, any tips?

My code: 

 

//Create transfer record
Set(
    varTransferRunOutput,
    Patch(
        Transfers,
        Defaults(Transfers),
        {
            Destination: LookUp(
                Sites,
                Name = First(
                    Split(
                        varInternalScan,
                        ","
                    )
                ).Result
            ),
            'Provided By': LookUp(
                Accounts,
                Account = GUID("ee2cce64-7459-eb11-a812-00224840faa6")
            ),
            Account: LookUp(
                Accounts,
                Account = cmbInternalAccount.Selected.Account
            ),
            Route: 'Route (Transfers)'.Internal,
            Date: Now()
        }
    )
);
//Create collection for all gallery items
ForAll(
    galInternalItem.AllItems,
    Collect(
        colInternalItemRun,
        {
            Transfer: LookUp(
                Transfers,
                Transfer = varTransferRunOutput.Transfer
            ),
            Account: cmbInternalAccount.Selected.Account,
            Item: GUID(lblInternalItemGUID.Text),
            Count: Value(txtInternalItemTransferQty.Text),
            'Source Location': lblSourceLocationGUID.Text,
            Status: 'Status (Transfer Items)'.Active
        }
    )
);
//Patch all collection records to Transfer Items table
ForAll(
    colInternalItemRun,
    Patch(
        'Transfer Items',
        {
            Transfer: LookUp(
                Transfers,
                Transfer = varTransferRunOutput.Transfer
            ),
            Account: LookUp(
                Accounts,
                Account = cmbInternalAccount.Selected.Account
            ),
            Item: LookUp(
                Devices,
                Device = GUID(lblInternalItemGUID.Text)
            ),
            Count: Value(txtInternalItemTransferQty.Text),
            'Source Location': LookUp(
                Sites,
                Site = GUID(lblSourceLocationGUID.Text)
            )
        }
    )
);

 

 

Three duplicate values from Patch statement: 

FrankKelp_0-1678115117614.png

 

Many thanks! 

 

Frank

1 ACCEPTED SOLUTION

Accepted Solutions

@APowerAppNewb not usre what is going on with yours, I created a form in powerapps for a sp list, and also just made a custom spform from the list settings also via powerapps, and in both instances the default form datacard settings for a multipeople picker column patched in people I selected as expected

 

Not sure why you would need to add /patch/ to the SharePoint form it generates as this form is already setup to add the correct data types to your column, is this to pull the employee additions from somewhere else? I'd tend to keep that to powerapps and not the custom sharepoint form screen myself  (because I don't use sharepoint forms and  they behave differently sometimes from powerapps)

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

View solution in original post

7 REPLIES 7
TheRobRush
Super User
Super User

Patching will work much better if you do it in the opposite order,

 

 

ClearCollect(
     CollectionName(
                    ForAll(GalleryItems to collect,
                          {Structure:Item})));

Patch(SourceToPatchTo, 
     ForAll(CollectionYouMade, CanBeJustThisRecordIfYouStructureABoveCollectForAllSameAsThisSourceIsLaidOutOtherwise  {ColumNames:ThisRecord.Data}))

 

 

ForAll does not behave exactly same as we'd be used to in programming, but more liek returns a list of items then you work with it. If you put it at top then you repeat the same list over and over. It works in some situations, but more often than not you will get unexpected resutls

 

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

Hi @TheRobRush ,

 

Many thanks for your reply, it was very helpful. 

 

A situation I am now running into is that it doesn't accept 

ThisRecord.Item

Or

ThisRecord.Account

 

The error message I receive is that I  "Cannot use a non-record value in this context" - When I remove the item & account column there error disappears. 

 

Both columns are lookup columns in the patch destination table. 

 

FrankKelp_0-1678117290928.png

 

 

What is the best way to navigate this? 

 

I tried two different approaches: 

 

1. 
Patch(
    'Transfer Items',
    ForAll(
        colInternalItemTransfer,
        {
            Transfer: ThisRecord.Transfer,
            Count: ThisRecord.Count,
            Status: ThisRecord.Status,
            Item: ThisRecord.Item,
            Account: ThisRecord.Account,
            'Source Location': ThisRecord.'Source Location'
            )
        }
    )
);

2. 
Patch(
    'Transfer Items',
    ForAll(
        colInternalItemTransfer,
        {
            Transfer: ThisRecord.Transfer,
            Count: ThisRecord.Count,
            Status: ThisRecord.Status,
            Item: LookUp(
                Devices,
                Device = GUID(lblInternalItemGUID.Text)
            ),
            Account: LookUp(
                Accounts,
                Account = ThisRecord.Account
            ),
            'Source Location': LookUp(
                Sites,
                Site = ThisRecord.Site
            )
        }
    )
);

 

Thanks Again!

 

Frank

 

TheRobRush
Super User
Super User

Error in the image you shared is due to that trying to patch in a table as opposed to a record. If that column is a text columns, boolean, etc anythign that should only have one piece of data in it, you need to filter that table result down to a record, or concat it. If that column is somethign like a choice column and you want to store everything in the returned table into it you will need to structure that data properly. CHoice columns are {Value:Info}, {Value:Info}, {Value:Info} a table column and the choice in it is always stored in a column titled value. It is best to structure that data properly in advance, but if that is not possible you should probably beable to do some sort of forall there, So Like for example Location: ForAll(referencetable As structure, {Value:structure.ColumnYouWant, or whatever it suggests you place behind that})

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!
FrankKelp
Helper I
Helper I

Hi @TheRobRush , 

 

So I thought I had my collection in the proper structure now, but maybe I am still not getting it. 

 

It was this: 

FrankKelp_0-1678188041067.png

I managed to get it to just show the individual value: 

FrankKelp_1-1678188094888.png

However, still receiving errors that it cannot access a non-record value in this context. 

 

I tried concat with transfer field to see if it worked, like so: 

ForAll(
    galInternalItem.AllItems,
    Collect(
        colInternalItemTransfer,
        {
            Transfer: Concat(
                Filter(
                    Transfers,
                    Transfer = varTransferGUID.Transfer
                ),
                Transfer
            ),
            Account: cmbInternalAccount.Selected.Account,
            Item: GUID(lblInternalItemGUID.Text),
            Count: Value(txtInternalItemTransferQty.Text),
            'Source Location': lblSourceLocationGUID.Text,
            Status: 'Status (Transfer Items)'.Active
        }
    )
);


Still won't accept it. 

 

I don't understand that if the raw values for each row are in the collection why isn't the patch statement accepting it? 

Patch(
    'Transfer Items',
    ForAll(
        colInternalItemTransfer,
        {
            Transfer: ThisRecord.Transfer,
            Account: ThisRecord.Account,
            Item: ThisRecord.Item,
            Count: ThisRecord.Count,
            'Source Location': ThisRecord.'Source Location'
        }
    )
);


Many thanks again, 

 

Frank. 

TheRobRush
Super User
Super User

Can you send a screenshot of the patch code, as written above, and the error it is showing you?

 

And also, in the meantime, make a gallery. press the button that does the collect of your data (also before you test this add a Clear(colInternalItemTransfer); before it so that collection doesn't have any leftovers. Then make that gallery's items colInternalItemTransfer and see if it gives you any errors too.

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

Hey RobRush, I am running into a similar problem as the original OP. I have a SharePoint Form that I am customizing in Power Apps. The particular challenge I am running into is trying to add multiple people to a multiperson column. I tried using the default update, but got an error message: "Network error when using Patch function: The requested operation is invalid". From there, I tried to set up a collection to catch the users being added to the combo box as follows:

ClearCollect(
    collectionRL,
    ForAll(
        DataCardValue11.SelectedItems,
        {
            '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
            Department: "",
            Claims: "i:0#.f|membership|" & Email,
            DisplayName: DisplayName,
            Email: 'Email',
            JobTitle: "",
            Picture: ""
        }
    )
)

From there, I tried to use a ForAll in the Update of the Data Card:

ForAll(
    collectionRL,
    {
        '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
        Department: "",
        Claims: "i:0#.f|membership|" & Email,
        DisplayName: DisplayName,
        Email: Email,
        JobTitle: "",
        Picture: ""
    }
)

I've confirmed that the collection is generating a list of information with multiple records. Neither of these solutions are working. For your final recommendation of using the Patch approach, where would I position that? In the OnSuccess option for the SharePoint form? And if it goes there, what would the final code look like? The multi-person column is called RLs.

@APowerAppNewb not usre what is going on with yours, I created a form in powerapps for a sp list, and also just made a custom spform from the list settings also via powerapps, and in both instances the default form datacard settings for a multipeople picker column patched in people I selected as expected

 

Not sure why you would need to add /patch/ to the SharePoint form it generates as this form is already setup to add the correct data types to your column, is this to pull the employee additions from somewhere else? I'd tend to keep that to powerapps and not the custom sharepoint form screen myself  (because I don't use sharepoint forms and  they behave differently sometimes from powerapps)

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (3,027)