cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BigE
Helper II
Helper II

Delegation on filtered patch to SharePoint list

I'm running into a delegation warning on some of my submits. Here is my formula for a single checkbox:

Patch(Datasource, First(Filter(Datasource, ID=varEditItem)), {checkbox:true}));

 

The above works and patches without any issues but I'm concerned about the delegation. I tried using LookUp instead and although I don't have a delegation warning, nothing submits to the datasource. I get not errors, just nothing happens.

Patch(Datasource, LookUp(Datasource, ID=varEditItem), {checkbox:true}))

 

Is there another way to make this work? I have a few of these popping up all over the place and would love to see them gone.

2 ACCEPTED SOLUTIONS

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @BigE ,

Is your data source a SP List?

 

If your data source is a SP List, I think the formula you provided should work without any Delegation issue. The LookUp function could be delegated with the SP List, and the ID field could not delegated with '=' operator.

Please check the following article for more details:

https://docs.microsoft.com/en-us/connectors/sharepointonline/#power-apps-delegable-functions-and-ope...

 

According to the LookUp formula that you mentioned, I found that you have a extra ')' at the end of your formula, please remove it, and modify it as below:

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: true
       }
)               // do not add extra ')' close bracket here

 

Please make sure the varEditItem variable is populated with proper Item ID value in your app. In addition, you could also consider try the following UpdateIf formula:

UpdateIf('SP List', ID = varEditItem, {checkbox: true})

or

UpdateIf('SP List', ID = BrowseGallery1.Selected.ID, {checkbox: true})

Note: The checkbox represents the Yes/No type column in your SP List. Please also consider set the "Data row limit for Non-Delegable queries" option to maximum value -- 2000 in Advanced settings of your App settings.

 

Please consider take a try with above solution, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Thanks for the input @v-xida-msft . By using your following statement I was able to make the patch work.

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: If(
                      Checkbox1.Value = true,
                      true,
                      false
                   )
       }
)  

However, I noticed something when I was testing, don't know how I missed it throughout this entire process. I have two identical controls on this screen and each are only visible to a logged in user type set by a variable. Somehow I had these switched and this is where most of my issues were coming up. While the above Patch works, I have a shorter statement that does the same:

On Check:
Patch(Datasource, LookUp(Datasource, ID=varEditItem), {SPColumn:true}) 

Thanks for all the help in this, I'm at the very least learning new techniques and ways to approach issues withing PowerApps!



View solution in original post

10 REPLIES 10
KrishnaV
Community Champion
Community Champion

Hi @BigE ,

 

Is your checkbox a choice filed? then try this:

Patch(SampleList, First(Filter(SampleList, ID=4)), {Status:{Value:"Yet-ToStart"}})

In the above formula Status is a choice file in my SharePoint List.

 
I hope this resolved your issue if you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
Krishna
If this post helps you give a 👍 and if it solved your issue consider Accept it as the solution to help the other members find it more.

 



I hope this resolved your issue if you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
KrishnaV
Business Applications MVP, Microsoft Certified Trainer
Twitter | Linkedin | YouTube | GitHub
If this post helps you give a THUMS-UP and if it solved your issue consider Accept it as the solution to help the other members / new members of the community.

Anonymous
Not applicable

@BigE 

A few things you could try

 

1. Use UpdateIf() instead of Patch() when updating records. Patch is ok for new records but UpdateIf() seems to work better on record updates, for some weird reason

 

2. Double-checkhow you are creating varEditItem and make sure it's a number eg if it's a Text value wrap it n Value() to convert it

 

3. What column type is 'checkbox'? If it's a SharePoint Yes/No column then these can cause delegation issues. If I ever need to use a Yes/No column in my app/s I create a Choice column with choices Yes, No because these columns don't create any delegation issues for my apps

 

Hopefully one of these gives you a solution?

 

As a side note, I did notice that you have any extra brace on the end of your formula but I figured that was a typo. If not,and there's more to your formula than you've shown, this may be the delegation issue reason.

@Anonymousand @KrishnaV , thanks for the reply. For the variable, I'm setting it on the click on an item in a gallery: Set(varEditItem,ThisItem.ID) which is giving my a numerical value. I am using a Yes/No column in SharePoint to match up with my Checkbox boolean value. I tried replacing Patch() with the UpdateIf() but I received a bunch of errors. Also, the extra ")" was added to close out my clear collect that I failed to add to my initial statement above.

Anonymous
Not applicable

@BigE 

Id try replacing your Yes/No column with a Choice column. You really should avoid these columns if you are using them in PowerApps.

Hi @BigE ,

 

Unfortunately, the Yes/No column in SharePoint with PowerApps is not working as appropriate. Rather you make that column as a choice with Yes/No.


I hope this resolved your issue if you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
Krishna
If this post helps you give a 👍 and if it solved your issue consider Accept it as the solution to help the other members find it more.
 

 



I hope this resolved your issue if you see any challenge/need further help please let me know I am always happy to do it for my community.

Regards,
KrishnaV
Business Applications MVP, Microsoft Certified Trainer
Twitter | Linkedin | YouTube | GitHub
If this post helps you give a THUMS-UP and if it solved your issue consider Accept it as the solution to help the other members / new members of the community.

v-xida-msft
Community Support
Community Support

Hi @BigE ,

Is your data source a SP List?

 

If your data source is a SP List, I think the formula you provided should work without any Delegation issue. The LookUp function could be delegated with the SP List, and the ID field could not delegated with '=' operator.

Please check the following article for more details:

https://docs.microsoft.com/en-us/connectors/sharepointonline/#power-apps-delegable-functions-and-ope...

 

According to the LookUp formula that you mentioned, I found that you have a extra ')' at the end of your formula, please remove it, and modify it as below:

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: true
       }
)               // do not add extra ')' close bracket here

 

Please make sure the varEditItem variable is populated with proper Item ID value in your app. In addition, you could also consider try the following UpdateIf formula:

UpdateIf('SP List', ID = varEditItem, {checkbox: true})

or

UpdateIf('SP List', ID = BrowseGallery1.Selected.ID, {checkbox: true})

Note: The checkbox represents the Yes/No type column in your SP List. Please also consider set the "Data row limit for Non-Delegable queries" option to maximum value -- 2000 in Advanced settings of your App settings.

 

Please consider take a try with above solution, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks @v-xida-msft, I tried each way and nothing will patch the update except for what I currently have published. Is this happening because I have this patch associated with a checkbox? Should I have a button or does that really matter?

Hi @BigE ,

I agree with you. If the Patch formula does not work with the Checkbox, please consider execute your formula in a Button. Please set the OnSelect property of a Button to following:

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: If(
                      Checkbox1.Value = true,
                      true,
                      false
                   )
       }
)  

Note: I assume there is a column called "checkbox" in your data source.

 

If you still want to execute your Patch formula within your Checkbox control, please set the OnSelect property of the Checkbox to following:

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: If(
                      Checkbox1.Value = true,
                      true,
                      false
                   )
       }
)  

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks for the input @v-xida-msft . By using your following statement I was able to make the patch work.

Patch(
       Datasource, 
       LookUp(Datasource, ID = varEditItem), 
       {
         checkbox: If(
                      Checkbox1.Value = true,
                      true,
                      false
                   )
       }
)  

However, I noticed something when I was testing, don't know how I missed it throughout this entire process. I have two identical controls on this screen and each are only visible to a logged in user type set by a variable. Somehow I had these switched and this is where most of my issues were coming up. While the above Patch works, I have a shorter statement that does the same:

On Check:
Patch(Datasource, LookUp(Datasource, ID=varEditItem), {SPColumn:true}) 

Thanks for all the help in this, I'm at the very least learning new techniques and ways to approach issues withing PowerApps!



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