cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Count Condition Update

I'm getting a delegation error with the below.

 

Is there anything I can do to fix this issue?

 

Also, how can I update the condition to include 'count only those Parks with the name "blahblah', rather than counting all Parks?

 

Better yet, add the following to the below 'and count only those Parks that match the content of ComboBox1'.

 

CountIf(ParkSnapShotDetailList,ECPark="Yes")

2 ACCEPTED SOLUTIONS

Accepted Solutions
poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 


@Anonymous wrote:

Also, the Member List will NEVER exceed 2000 items, so my assumption was this straying from the known delegation norms could be achieved with little to no adverse impact.

 



If that is the case, then maybe it's because of this in your screenshot:

 

ParkAlphaCmboBox.SearchText

 

Unless there is typed text in the ComboBox, this will be blank by default, hence the zero.

 

Try a simpler model first like an Input Text Field. See if it works. Then adjust the ComboBox one if it has to be ComboBox.

 

If you can truly guarantee what you said about the 2000 never being exceeded for the member list - then @Pstork1 suggestion will work for you, even in production. (and technically, you have to guarantee it only for the non-delegable outer part, if you do that carefully, it can be even more, as @Pstork1 mentioned as well)

 

Check if above helps. 

 

We are also checking if your scenario is possible with delegation only in some other wild way, still keeping SharePoint List (if it even is possible).

View solution in original post

poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 

There is a solution to do it with delegation.  We share with you here in case you are interested.

By the way, by delegation, we mean it for real, we tested with a super low delegation limit of 1 set on the App. Because actually even if the yellow triangle doesn't show, it may still be using a non-delegable function under the hood, the only way to be sure, is set delegation limit to 1, have more than 1 matching item for the Filter, and have way more than 1 total item as well (which we tested with).

 

When we tested with delegation limit of 1, we actually could confirm by testing that even the most basic Filter formula against SharePoint List, with just something equals something else - the most basic supported Filter -  would be actually non-delegable under the hood when using it directly - yes, even that most basic one. 

 

The solution to make it delegable, is to place that same Filter formula in Items property of a Gallery first and then just CountRows on that Gallery. This is the only way we could find that works. Otherwise, even the most basic Filter turns out to be non-delegable - even when we got it to show no warnings and even when we did not use ANY counting functions, even then it was returning 1 record in our case instead of 4 until we did it this way! 

 

You could also obviously just have the Gallery show all items and have CountRows against the Filter in the Gallery from somewhere else like a Text field, this works too, but this is less ideal to do it this way as the Gallery would load all the records first in memory and could overfill with too much, potentially affecting performance negatively - you would circumvent the delegation limit and get all the records to display in the Gallery. but with big penalty. Imagine that huge scrollbar on that Gallery (and that would still be there with all those tons of records, even if you made the Gallery Invisible)!

 

Because the Filter simply just works properly in the Items Property of the Gallery itself ,  it is better to put it there with the Filter ,then just CountRows on all the records after that, as the Gallery itself will properly filter with delegation and have the lower number of records as well, not all the records, which could be orders of magnitude better for performance than loading literally all the records in a Gallery first. You can just make the Gallery invisible if you want, the Gallery is just to get this to work - because it only works doing this in a Gallery when we tried it.

 

Note that our test should check out. Our delegation limit is 1. If it was non-delegable, we should not have been able to get more than 1 record at most (which happened during testing many times such as when using a Collection, which does not throw a warning but this is a non-delegable technique too - it even returned only one record, when using the Filter directly just to get the Table of records - when it was not in a Gallery and without using CountRows - the Table itself had just one record every time!), and actually, it would not have seen more than 1 record in the first place, so it was more likely to return zero. Only in Gallery, we got it to return 4 records in our test on a delegation limit of 1.

 

Here's details:

 

SharePoint List:

 

List823y5.png

 

 

 

 

App:

gallerydelegateshpt92345.gif

 

 

 

Solution Summary:

 

In the Items Property of a Gallery:

 

 

 

Filter(List01,ParkName=TextInput1.Text)

 

 

 

In the Text Property of a Label:

 

 

 

CountRows(Gallery1.AllItems)

 

 

 

 

And finally, if the Gallery is not needed for UI, just set Visible to false for the Gallery.

 

Check if above helps you @Anonymous 

View solution in original post

12 REPLIES 12
Pstork1
Most Valuable Professional
Most Valuable Professional

You can't get rid of the delegation warning because CountIf() isn't delegable.  However, if you use a delegable function to pre-filter the data being counted to get it below the threshold then you can ignore the delegation warning.  See the example below

CountIf(Filter(ParkSnapShotDetailList, name="blahblah"),ECPark="Yes")


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Anonymous
Not applicable

Is there a way to make the following work?

 

     CountIf(Filter(MemberList, Park=ParkAlphaCmboBox.SelectedItems),ECMem="Yes")

poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 

Unless it is really, absolutely impossible otherwise, we would not recommend to ignore the delegation warning for any production scenario for almost any reason, as at some point, the number may just go above the count from the latter part of expression, so it would always be a risky condition that could break at any time. To place outer function that is non-delegable with reliance on the inner function returning less than the delegable limit is currently considered unsuitable for production in our opinion, in 100% of our current production cases, and we almost never even accept to leave it like that for most testing or development purposes either.

 

We would first recommend try to just use something other than CountIf and just make sure it is delegable in whatever way you can, even if it is ultimately more contrived, as long as it is some way that is delegable it will always be better if it is some other way than by using a non-delegable function. 

 

That non-delegable outer function composition there on an inner function that returns less than delegable limit and ignoring the delegation warning, should really be the last resort. If you ever resort to it, write it down in a documentation with a big red flag, every time you did this - you will have to maintain that specific part where you used a sub expression to get it down to lower number, because if that sub expression ever goes past the delegation limit, that will make it not work properly anymore, and there will be no warning after that in production, it will just start missing records. For this reason, we do not ever leave delegation warning there, and not even for one production use case. 

 

Also remember to do one more thing if you really must go this way - in App Settings for the app you do this with, you should raise the default non-delegable limit from 500 to 2000 - you'll need it - and it won't be nearly enough in many production cases, even the max of 2000. The magic number is 2000 because that is the highest the  App non-delegable limit setting will allow, even if you change it, but the default is 500, you may want to raise it to 2000.

 

As for what that specific function would be which would be delegable in your scenario, that may depend, what is your current data source right now - is it SharePoint List? Please confirm this in next reply and if we can we might check into the delegable version of the specific function for you that would count all the parks that meet specific condition, or any equivalent way that might avoid pitfalls of simply ignoring the delegation warning.

Anonymous
Not applicable

Thank you for the detail.

 

Yes, SP list.

 

What else counts other than 'Count...'? Not sure how this can be accomplished. I'll look around for alternative.

 

Thank you.

Pstork1
Most Valuable Professional
Most Valuable Professional

If the ParkAlphaCmboBox is a multi select rather than a single select you are going to have a problem with the filter.  Otherwise, that should work as long as the Filter gets you below the data row limit (500 default, 2000 max)



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Anonymous
Not applicable

I'm already at 2000.

 

I'm using the following, or a version thereof based on content desired, in four TextInput fields. 

 

The are all returning '0'.

     

3csman_0-1608054582982.png

 

Circling back on the 'never ever CountIf', is there another condition that counts that won't kick back the delegation error that I can try?

Anonymous
Not applicable

Also, the Member List will NEVER exceed 2000 items, so my assumption was this straying from the known delegation norms could be achieved with little to no adverse impact.

 

Thanks!

poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 


@Anonymous wrote:

Also, the Member List will NEVER exceed 2000 items, so my assumption was this straying from the known delegation norms could be achieved with little to no adverse impact.

 



If that is the case, then maybe it's because of this in your screenshot:

 

ParkAlphaCmboBox.SearchText

 

Unless there is typed text in the ComboBox, this will be blank by default, hence the zero.

 

Try a simpler model first like an Input Text Field. See if it works. Then adjust the ComboBox one if it has to be ComboBox.

 

If you can truly guarantee what you said about the 2000 never being exceeded for the member list - then @Pstork1 suggestion will work for you, even in production. (and technically, you have to guarantee it only for the non-delegable outer part, if you do that carefully, it can be even more, as @Pstork1 mentioned as well)

 

Check if above helps. 

 

We are also checking if your scenario is possible with delegation only in some other wild way, still keeping SharePoint List (if it even is possible).

poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 

There is a solution to do it with delegation.  We share with you here in case you are interested.

By the way, by delegation, we mean it for real, we tested with a super low delegation limit of 1 set on the App. Because actually even if the yellow triangle doesn't show, it may still be using a non-delegable function under the hood, the only way to be sure, is set delegation limit to 1, have more than 1 matching item for the Filter, and have way more than 1 total item as well (which we tested with).

 

When we tested with delegation limit of 1, we actually could confirm by testing that even the most basic Filter formula against SharePoint List, with just something equals something else - the most basic supported Filter -  would be actually non-delegable under the hood when using it directly - yes, even that most basic one. 

 

The solution to make it delegable, is to place that same Filter formula in Items property of a Gallery first and then just CountRows on that Gallery. This is the only way we could find that works. Otherwise, even the most basic Filter turns out to be non-delegable - even when we got it to show no warnings and even when we did not use ANY counting functions, even then it was returning 1 record in our case instead of 4 until we did it this way! 

 

You could also obviously just have the Gallery show all items and have CountRows against the Filter in the Gallery from somewhere else like a Text field, this works too, but this is less ideal to do it this way as the Gallery would load all the records first in memory and could overfill with too much, potentially affecting performance negatively - you would circumvent the delegation limit and get all the records to display in the Gallery. but with big penalty. Imagine that huge scrollbar on that Gallery (and that would still be there with all those tons of records, even if you made the Gallery Invisible)!

 

Because the Filter simply just works properly in the Items Property of the Gallery itself ,  it is better to put it there with the Filter ,then just CountRows on all the records after that, as the Gallery itself will properly filter with delegation and have the lower number of records as well, not all the records, which could be orders of magnitude better for performance than loading literally all the records in a Gallery first. You can just make the Gallery invisible if you want, the Gallery is just to get this to work - because it only works doing this in a Gallery when we tried it.

 

Note that our test should check out. Our delegation limit is 1. If it was non-delegable, we should not have been able to get more than 1 record at most (which happened during testing many times such as when using a Collection, which does not throw a warning but this is a non-delegable technique too - it even returned only one record, when using the Filter directly just to get the Table of records - when it was not in a Gallery and without using CountRows - the Table itself had just one record every time!), and actually, it would not have seen more than 1 record in the first place, so it was more likely to return zero. Only in Gallery, we got it to return 4 records in our test on a delegation limit of 1.

 

Here's details:

 

SharePoint List:

 

List823y5.png

 

 

 

 

App:

gallerydelegateshpt92345.gif

 

 

 

Solution Summary:

 

In the Items Property of a Gallery:

 

 

 

Filter(List01,ParkName=TextInput1.Text)

 

 

 

In the Text Property of a Label:

 

 

 

CountRows(Gallery1.AllItems)

 

 

 

 

And finally, if the Gallery is not needed for UI, just set Visible to false for the Gallery.

 

Check if above helps you @Anonymous 

Helpful resources

Announcements

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

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  

Copilot Cookbook Challenge | Week 1 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

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. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

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