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

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

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

 

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!

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. 

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

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!

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.    

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

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  

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 (3,733)