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

Invalid Argument Type Error on Button to Patch Collection

I have built an editable table displaying customers in the manner described by @Reza in one of his Youtube videos. I am trying to use a button to patch additions or changes to that collection to a customer table called Custs. The collection is call colCustUpdates.

 

As instructed by Reza, I have added a hidden button to the gallery with the OnSelect property set as shown below. The purpose is to check if a collection is in the Cust table. If it is present, the collection should update the table. Otherwise, the collection should be added to the table. The unique field created by Power Apps in the Cust table is also called Cust.

 

If(
ThisItem.Cust in colCustUpdates.Cust,
Update(
colCustUpdates,
LookUp(
colCustUpdates,
Cust=ThisItem.Cust
),
{
Cusname: Cusname.Value,
SCS_ID: SCS_ID.Selected.Value,
Active: Active.Selected.Value,
Auto_ID: Auto_ID.Value,
Shortname: Shortname.Value,
Region: Region.Selected.Value,
SOM: SOM.Value,
Cust: ThisItem.Cust
}
),
Collect(
colCustUpdates,
{
Cusname: Cusname.Value,
SCS_ID: SCS_ID.Selected.Value,
Active: Active.Selected.Value,
Auto_ID: Auto_ID.Value,
Shortname: Shortname.Value,
Region: Region.Selected.Value,
SOM: SOM.Value,
Cust: ThisItem.Cust
}
)
)

 

The button to save the collection has the following OnSelect property.

 

Patch(
Custs,
colCustUpdates
);
Clear(colCustUpdates);

 

The button has the error "Invalid Argument Type (Table). Expecting a Record value instead."

 

I've been trying for hours to figure out where the problem is. I believe it might be related to the Active field which is a Yes/No type. But, that's just a guess. Very open to suggestions.

1 ACCEPTED SOLUTION

Accepted Solutions

The Patch function requires three arguments to update records in a data source: the data source itself (Custs, in your case), the record to be updated (or a table of records), and the updates to be made. The overload with 2 parameters is used to merge records, which is not what you need.

In your case, you can use the ForAll function to iterate through the collection, and patch the items to the data source. The example below is a general case that should work whether the items are being inserted or updated, but you can simplify it if you know that it will be all inserts (or all updates):

ForAll(
    colCustUpdates As c,
    With(
        { toUpdate: LookUp(Custs, Cust = c.Cust) },
        Patch(Custs, Coalesce(toUpdate, Defaults(Custs)), c)
    )
)

If you know that all of the items in the collection will be inserted, the expression can be simplified: 

ForAll(colCustUpdates, Patch(Custs, Defaults(Custs), ThisRecord))

Similar with the case where you know that all the items in the collection will be updated:

ForAll(colCustUpdates As c, Patch(Custs, LookUp(Custs, Cust = c.Cust), c))

Hope this helps!

View solution in original post

4 REPLIES 4
Nick_F
Frequent Visitor

Some additional info:

  • I have verified all field names are spelled correctly
  • When I check the collection, I see all field values are correct

So, it appears the issue is with the Patch command. 

The Patch function requires three arguments to update records in a data source: the data source itself (Custs, in your case), the record to be updated (or a table of records), and the updates to be made. The overload with 2 parameters is used to merge records, which is not what you need.

In your case, you can use the ForAll function to iterate through the collection, and patch the items to the data source. The example below is a general case that should work whether the items are being inserted or updated, but you can simplify it if you know that it will be all inserts (or all updates):

ForAll(
    colCustUpdates As c,
    With(
        { toUpdate: LookUp(Custs, Cust = c.Cust) },
        Patch(Custs, Coalesce(toUpdate, Defaults(Custs)), c)
    )
)

If you know that all of the items in the collection will be inserted, the expression can be simplified: 

ForAll(colCustUpdates, Patch(Custs, Defaults(Custs), ThisRecord))

Similar with the case where you know that all the items in the collection will be updated:

ForAll(colCustUpdates As c, Patch(Custs, LookUp(Custs, Cust = c.Cust), c))

Hope this helps!

Thank you, Carlos! All of your options appear to resolve the invalid argument type error.

 

I am now getting a strange error: "The column 'Active' does not exist. The column with the most similar name is 'Active'."

 

Active is identified as "Active: Active.Selected.Value". Is that appropriate for a Yes/No toggle column?

 

Nick

Hello @Nick_F ,

The difference between your solution and Reza's is that the first collection he was doing was in a Gallery with the data source, with the Checkbox control under the On Check property with the following code:

Collect(colUpdates, ThisItem)

What this does is critical for the procedure explained by him. It creates the collection with the data source's metadata.

In your case where is your table located? SharePoint, Dataverse, SQL? Let's assume it's on SharePoint.

When you use Collect in your code (below) to create a new record in your table, Power Apps doesn't know what's that table's metadata, i.e. columns, column types, etc. 

If(
    ThisItem.Cust in colCustUpdates.Cust,
    Update(
        colCustUpdates,
        LookUp(
            colCustUpdates,
            Cust=ThisItem.Cust
        ),
        {
            Cusname: Cusname.Value,
            SCS_ID: SCS_ID.Selected.Value,
            Active: Active.Selected.Value,
            Auto_ID: Auto_ID.Value,
            Shortname: Shortname.Value,
            Region: Region.Selected.Value,
            SOM: SOM.Value,
            Cust: ThisItem.Cust
        }
    ),
    Collect(
        colCustUpdates, {
            Cusname: Cusname.Value,
            SCS_ID: SCS_ID.Selected.Value,
            Active: Active.Selected.Value,
            Auto_ID: Auto_ID.Value,
            Shortname: Shortname.Value,
            Region: Region.Selected.Value,
            SOM: SOM.Value,
            Cust: ThisItem.Cust
        }
    )
)

You can create a temporal collection based on your data source (first record) to create the metadata, then clear the temporal collection and then copying it to your collection with this code:

ClearCollect(colTemp, First(Custs));
Clear(colTemp);
Collect(ColCustUpdates, colTemp);

This way you'll have your metadata in the collection colCustUpdates and it will be blank. Then you can use Collect to save to your collection the new data.

The final trick you're missing from Reza is that when you want to create a new record, you have to drop your table's unique identifier column, e.g. ID in the case of SharePoint, and passing the information to a new collection, like this:

ClearCollect(
     colToPatch,
     DroppColumns(
          colCustUpdate,
          "ID",
     )
)

Now Power Apps knows that this collection is to create a new record, and you can save to your data source with Patch:

Patch(Custs, colToPatch)

Hope it helps.

Regards,

Fernando

 

If this helped please give it a thumbs up. Even if your post is already solved it could benefit others.

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 (1,829)