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

Filter formula error

I'm getting an error when using IF statements within a patch? Is this not allowed? The error I get is 'Invalid ArgumentType' but does not underline or show me anything else.

 

Patch(
    '[dbo].[tbLink]',
    {LinkID: Value(LinkID)},
    {AssignedDate: DCR_1.SelectedDate},
    {AssignedUser: User.Text},
    {LinkComment: Comment.Text},
    {SourceID: 1},
    {TargetID: 1},
    {
        Type: Text(
            If(
                Type.Text = "Related to",
                "Related",
                "Parent-Child"
            )
        )
    })


Thanks!

2 ACCEPTED SOLUTIONS

Accepted Solutions

@LRVinNC  actually, yes, you can use the If statement and many others within the Patch function without having to wrap them like the samples.  This I do in many apps, it's a necessity as there are many conditions that need to be accounted for with the columns!

 

@jesenavaranjan 

Your formula, at a a glance, seems to be fine, so there is either something going on with the definition of some of those items or something impacting the designer.

I would however, make a change to the formula to be the following:

Patch(
    '[dbo].[tbLink]',
    {LinkID: Value(LinkID),
     AssignedDate: DCR_1.SelectedDate,
     AssignedUser: User.Text,
     LinkComment: Comment.Text,
     SourceID: 1,
     TargetID: 1,
     Type: If(Type.Text = "Related to", 
                "Related",
                "Parent-Child")
     }
)

Try the above formula and see if you still have the issue.  

If so, try to narrow it down.  If you suspect issues in the If statement, then first, change the "Type.Text" to "true".  If the problem goes away, then there is an issue with the Type.Text.  If not, then replace the whole If statement with one value - let's say "Related", and see if the issue still exists.

Hopefully one of the above will lead you to a clue or a solution.

_____________________________________________________________________________________
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

@KroonOfficeSol 

Good call!  In my haste to look at the "If" part, totally glossed over the sourceRecord parameter missing!  Kind of think that would be helpful 😉

 

_____________________________________________________________________________________
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

5 REPLIES 5
LRVinNC
Resident Rockstar
Resident Rockstar

No, you cannot use the If within the Patch, but you can wrap the Patch statement in an If to accomplish this. 

This could be like the case in this post, https://powerusers.microsoft.com/t5/Expressions-and-Formulas/Patch-With-Conditions/td-p/107780, where you want to set a value and use that value in your patch or it could be a situation like the example code shown in the question on this post https://powerusers.microsoft.com/t5/Expressions-and-Formulas/Patch-with-if/td-p/171724 where you want to actually make your Patch statement vary slightly based on an If.  

 

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

@LRVinNC  actually, yes, you can use the If statement and many others within the Patch function without having to wrap them like the samples.  This I do in many apps, it's a necessity as there are many conditions that need to be accounted for with the columns!

 

@jesenavaranjan 

Your formula, at a a glance, seems to be fine, so there is either something going on with the definition of some of those items or something impacting the designer.

I would however, make a change to the formula to be the following:

Patch(
    '[dbo].[tbLink]',
    {LinkID: Value(LinkID),
     AssignedDate: DCR_1.SelectedDate,
     AssignedUser: User.Text,
     LinkComment: Comment.Text,
     SourceID: 1,
     TargetID: 1,
     Type: If(Type.Text = "Related to", 
                "Related",
                "Parent-Child")
     }
)

Try the above formula and see if you still have the issue.  

If so, try to narrow it down.  If you suspect issues in the If statement, then first, change the "Type.Text" to "true".  If the problem goes away, then there is an issue with the Type.Text.  If not, then replace the whole If statement with one value - let's say "Related", and see if the issue still exists.

Hopefully one of the above will lead you to a clue or a solution.

_____________________________________________________________________________________
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 learn something new (usually LOTS of something new) every day.  Thanks!

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

@jesenavaranjan 

 

I'm also missing the second argument for the patch. Updated from the formula of @RandyHayes 

Patch(
    '[dbo].[tbLink]',
Defaults( '[dbo].[tbLink]'),
    {LinkID: Value(LinkID),
     AssignedDate: DCR_1.SelectedDate,
     AssignedUser: User.Text,
     LinkComment: Comment.Text,
     SourceID: 1,
     TargetID: 1,
     Type: If(Type.Text = "Related to", 
                "Related",
                "Parent-Child")
     }
)

Maybe that's the reason for the error.

 

Still an error, then maybe one of the columns is not plain text, but an object. This could be the case when SharePoint is your data source?

 

Btw, in the formula bar, you don't always get a good error message. Sometimes the error message on the red marker on the canvas is more informative. You can see this by hover over the red marker. So you can try this.

 

Hope this helps also.

 

Paul

@KroonOfficeSol 

Good call!  In my haste to look at the "If" part, totally glossed over the sourceRecord parameter missing!  Kind of think that would be helpful 😉

 

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

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 (4,341)