cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JimmyWork
Resident Rockstar
Resident Rockstar

Delegation question

Hi

 

In my powerapp im pulling data from a SharePoint list.

In some functions i use i filter that SharePoint list per user.

Now i wonder how delegation works if i do a countIf

CountIf(SharePointList, Lower(Requester.Email) = Lower(User().Email) && Status.Value="Closed")

If my list contains 5000 items will the countIf only work on the 500 first items for that specific user or for all items?

A single user will not pass 2000 items so i can raise this if needed to. But if it counts only works on the 500 first items then i will display the wrong information based on countIf?

 

And most important how do you workaround this delegation? And do i need to work around it based on my criteria above? 

3 ACCEPTED SOLUTIONS

Accepted Solutions

>>Or how can i actually test this?

Try using the monitor tool (far left of the screen in the vertical strip of icons - a spanner and screwdriver - click on that and then on Open Monitor).

With the monitor tool open, click on your buttons that fetch the data. You can then see in the monitor tool how much data was returned and view the first few rows of the data. You can use this to give you some idea of what is going on under the surface and whether your filters are being delegated to the data source.

You may get delegation issues with User().Email - PowerApps doesn't seem to always 'resolve' such references properly but you can force it by setting a label or variable to the value and then using that in your formula.

View solution in original post

@JimmyWork 

Have you tried this approach I suggested in an earlier post?

Create a new column in your datasource called assignedEmail. When requester is submitted to the datasource update the assignedEmail column at the using this code

Lower(Requester.Email)


Then put this code in the OnStart property of your app

Set(currentUserEmail, Lower(User().Email))


Finally, you can use this code to count the rows for a user. Notice that LOWER is no longer needed since we took steps earlier on to clean the data.

CountRows(Filter(SharePointList, assignedEmail = currentUserEmail && Status.Value="Closed"))


—-
Please Accept as Solution if this post answered your question so others may find it more quickly. If you found this post helpful consider giving it a Thumbs Up.

View solution in original post

Can someone explain why this happens.

I have delegation set to 500 in the app.

My list has 620 items.

If I put this in the gallery item it will show me all 620 items.

If i put it in a ClearCollect or a variable it will only show me 500 items.

 

Then i set the Gallery to colList and it only shows me 500 items, why?

 

If your filter is delegable, a gallery will initially bring back the first100 rows. As you scroll to the end of the gallery it will fetch the next 100 rows - this is because a delegable filter can be 'paged'. Only 100 rows are returned with each call so this is not exceeding the delegation limit, though the total number of items in your gallery can eventually be more than the delegation limit if you keep scrolling.

When you do a ClearCollect, you are not paging, but pulling all the data in one go, up to the delegation limit.

CountRows is not delegable (and nor is Count, even though it does not show the delegation warning!). To work out the count, PowerApps must pull back all the matching rows and then count them (very inefficient). If Count or CountRows was delegated you would get back just the number of rows (not the actual rows) as that would have been calculated server-side, so the actual rows would not need to be returned.

I don't know why Count shows as delegable (at least on SQL Server datasources) as the Count is not being calculated server-side. To get an efficient count with SQL you must create a view which returns just the Count and then call that.

View solution in original post

21 REPLIES 21

@JimmyWork 

This code would be more delegation friendly.  The FILTER function can find an infinite amount of rows.  Then the COUNTROWS function will count up to the first 2,000 rows assuming you have increased the delegation limit in the advanced settings menu.

 

CountRows(
    Filter(
        SharePointList,
        Requester.Email = User().Email
        && Status.Value="Closed"
    )
)

 

I would suggest not using the LOWER function anywhere in this formula.  LOWER cannot be delegated.  But the good news is that LOWER is probably not necessary here since the User().Email should have the same capitalized letters as Requester.Email.

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

 

@mdevaney Thank you for answering.

 

If i do not use lower i will not get the correct data due to users email can have both big and small letters resulting in a mismatch.

And  actually this wont give you a delegation warning: CountIf(SharePointList, Lower(Requester.Email) = Lower(User().Email))

But if i use your code i do get 3 delegation warnings and it will display the wrong amount.

@JimmyWork 
If you found a result that does not give you a delegation warning does that mean you found a solution?

@mdevaney Im tryinig to understand but sometimes lower give delegation sometimes not and im trying filter on more column and then i just end up with delegation. Im trying to work out if i can use ClearCollect or something?

 

Trying to filter this.

ClearCollect(RecordsTickets, Filter(SharePointList, Lower(Requester.Email) = Lower(User().Email) && Status.Value="Unassigned" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Assigned" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="In Progress" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Waiting for user response" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Waiting for external resource"))

In my experience, Count is not delegated even with SQL, even though PowerApps may not give a delegation warning (don't rely on the warning, especially if you have 'nested' filters, it will often give you the false impression that a formula is delegating when it isn't).

You can see this using the Monitor tool. Try Collecting based on the Count function and Collecting just for the Filter - in my tests I found they return exactly the same amount of data, so the 'Count' is clearly not being delegated.

If you are using SQL you could create a server-side view to group by the 'lower' of the email name and return the count, and then filter against that view. You may want to put the 'lower' of the email address you are looking for into a variable or text box as including 'lower' in the filter itself may break the delegation as @mdevaney points out.

If you are using SharePoint or CDS then I'm afraid you're at the mercy of the delegation limits AFAIK. Although I believe CDS can do a count in a 'roll up' field, these are not 'live' (data is refreshed periodically) so at best will only be telling you want the count was an hour ago (or whatever cycle the roll-up is refreshing on).

@PaulD1 Thank you for answering.

But can i do anything about my other formula to remove delegation?

 

ClearCollect(RecordsTickets, Filter(SharePointList, Lower(Requester.Email) = Lower(User().Email) && Status.Value="Unassigned" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Assigned" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="In Progress" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Waiting for user response" || Lower(Requester.Email) = Lower(User().Email) && Status.Value="Waiting for external resource"))

@JimmyWork
The most reliable method I could offer is this:

Create a new column in your datasource called assignedEmail. When requester is submitted to the datasource update the assignedEmail column at the using this code

Lower(Requester.Email)

Then put this code in the OnStart property of your app

Set(currentUserEmail, Lower(User().Email))

Finally, you can use this code to count the rows for a user. Notice that LOWER is no longer needed since we took steps earlier on to clean the data.

CountRows(
Filter(
SharePointList,
assignedEmail = currentUserEmail
&& Status.Value="Closed"
)
)

—-
Please Accept as Solution if this post answered your question so others may find it more quickly. If you found this post helpful consider giving it a Thumbs Up.

@mdevaney Thank you i will try this.

Sorry for this but Requester is actually the Author column just renamed

You could try something like...

 

CountRows(

Filter(

Filter(
SharePointList,
 Status.Value="Closed"
), lower(assignedEmail) = lower(currentUserEmail)
)

 

This should first return records where the status.value = "Closed" and this will be delegated (so you should get the first 500 (or 2000 if you have upped the delegation limit in advanced settings) matching records regardless of where they appear in the list.

The second (outer) filter will then work on the results of the first filter and finally you will count the rows.

If you know that at any given time, there should be fewer records with status.value="closed" than the delegation limit, you should get an accurate count (although you may not get great performance).

The issue here (sorry for repeating myself from other threads) is that SharePoint is not a database and does not have database type features (such as proper server-side queries). For these sort of requirements you really want SQL, but the licensing model makes it too expensive in most circumstances. 

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