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

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (4,035)