cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
larivibi
Advocate III
Advocate III

Delegation and Variable/Collections

I can clearly see the benefits of delegation when I populate a Gallery. The queries are fast to comeback with lots of data. But I am unable to store a "delegable" query into a variable (local or global) or into a collection. 
I have set the non delegable limit to 3 items, so I can see if delegation works.

The exact same formula works with delegation when using the Items property of a Gallery (it populates the gallery with 55 items), but only populates a collection or variable with 3 items (non delegable limit I set).

Is it impossible to store delegable queries into variables/collections ?

2 ACCEPTED SOLUTIONS

Accepted Solutions
RandyHayes
Super User
Super User

@larivibi 

That is correct.  It sets the maximum number of records in the session tables and thus the maximum number of records you can retrieve at one time - from ANY query - delegable or not.

 

To get a better understanding on the limit and delegation, I like to use the truck scenario.   

Let's say you have a truck that can only carry 10 boxes (record limit).  If you go to a store (datasource), you can return with 10 boxes.  If you ask the clerk to give you all the boxes with a blue label on the outside, they can easily do it (delegable query).  If they have 20 boxes with blue labels, they will give you the first 10 they find because you can only handle 10 boxes (delegable query with record limit).

If you ask them for all the boxes with blue lamps in them, they tell you - "we can't open the boxes and look", but we can give you the 10 boxes you can carry with you and then you can open them and see (non-delegable query with record limit).  So, you take your 10 boxes and open them to look and find that only 3 of them had blue lamps.  SO...you have 3 boxes with blue lamps - that is your result. 
The problem with a non-delegable query (as you know) is that YES, you got 3 blue lamps and you tell whoever you are getting them for that there are 3 blue lamps...but in reality the store still had a lot of other boxes that might also have blue lamps in them.

 

So, the obvious answer that everyone goes for is - just bump up the record limit to 2000 and cross your fingers.  Well, the real answer is to design your app and data to not only be delegable, but also to limit your records to only the amount you really need in the app.  Because, otherwise you are impacting performance loading up 2000 "boxes" into your truck all the time when you only needed 10 of them.

 

Hopefully that is clear and helpful for you.

 

EDIT: Oh, and again, the way the records come back for Galleries is different as the Gallery "pages" the results differently with the record limits and query.

_____________________________________________________________________________________
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

RandyHayes
Super User
Super User

@larivibi 

I'll start with the later part - Galleries were designed (IMO) around the fact that people seem to want to show thousands of records in a gallery - because their users really want to scroll through a lot of records to find what they want (sarcasm).  So, this causes issues with performance because not only does the app need to get all the data, but the gallery needs to render it all.  That is a pretty big memory footprint.  So, they made them to page on their own.  They will get a certain number of records first and then as the user scrolls down, continue to get the additional.  This minimized the initial performance issue and the memory issue.  So, they have that little gem in them.  It can be a blessing and a curse depending on how you use the Gallery.

 

For example, using your approach to having a Gallery be a "sub gatherer" in order to do a Distinct on it to get what you want (because yes, Distinct is not delegable).  So, let's say you have 2000 records in your datasource.  If you set the Gallery to that datasource to get the records and then do a Distinct on the AllItems of the Gallery, then you will run into problems because the Gallery will not have loaded all of the records...it has to page them on demand.  How do you demand them...you have to scroll to the bottom until it is no longer gathering new records.  This is problematic because you either have to have the user scroll it, or, if it is hidden, then you need to scroll it by selecting the last record with the Select function (select for a Gallery lets you not only select the gallery, but also a row).  The problem is...you need to specify the row - the last one.  But how do you know what number that is??  Well, you could CountRows on the datasource to get the number of rows - BUT, CountRows is not delegable!!  So, in your case, you would only count rows of 3.

 

The reality is that to do delegation properly and handle situations like this, you really have to think from the data side of things.  If you are using SQL for example, you can offload a lot of the non delegable actions into views.  Example, you can get the distinct in a view and then just get that view in your app (of course with 3 records as your limit, you'll still only get 3 records).  But, based on the above Gallery scenario, you could also have a view that returns the count of all the distinct...so you could select the last row in the gallery and have them all.

 

In the case of SharePoint, you have to plan for these things.  Planning around this is done in a few ways.  One would be to utilize PowerAutomate to create a separate list of all the distinct values.  You could also do it in PowerApps itself, but this is a good job for a flow.  Then, you will have a list with just the distinct values to work from and not need to issue the non-delegable Distinct function.  

How do you get a record count...well, you can't.  But, you can again plan around it with a flow.  If you have another list with even just a single record and a column for each data list that you are interested in and a numeric count of the records in those lists, then you can have flow fill in the current count of records and your app can just refresh that datasource and get the record count.

 

There are a lot of little ways to plan around delegation issues and record limits.  Most of it becomes very specific to the scenario as opposed to "do it like this all the time".  

 

As for the documentation...yes, there is a LOT of details missing in them about these situations.  I think they just left it up to the forum to fill in the blanks 😀

 

Hopefully all clear and helpful for you.

_____________________________________________________________________________________
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

7 REPLIES 7
RandyHayes
Super User
Super User

@larivibi 

Galleries perform their gathering of information differently than trying to put information in a collection.

If your record limit is set to 3 then you will only get 3 records on any particular formula...except in the case of a Gallery.  They "page" themselves differently.

 

However, your post is more in regard to record limit than it is to delegation.  Delegation is the factor of sending a "query" to the datasource to get results that the datasource can handle on its own.

Record limit has only to do with the maximum number of results you get back.

 

So if your record limit is set to 3, you will never get more than 3 records in return.  So, if you delegate a filter, you will only get 3 records back.

 

As for the variables and collections - unless there is some specific need for a duplicate snapshot of your data, avoid them.

 

I hope this is helpful for you.

 

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

Thank You for the info,

 

just to be sure, this here :

larivibi_0-1620176744001.png

...is not only setting limit for non delegable queries, but also the limit of records obtained by a delegable query when stored into a variable or collection?
Do I understand correctly ?

RandyHayes
Super User
Super User

@larivibi 

That is correct.  It sets the maximum number of records in the session tables and thus the maximum number of records you can retrieve at one time - from ANY query - delegable or not.

 

To get a better understanding on the limit and delegation, I like to use the truck scenario.   

Let's say you have a truck that can only carry 10 boxes (record limit).  If you go to a store (datasource), you can return with 10 boxes.  If you ask the clerk to give you all the boxes with a blue label on the outside, they can easily do it (delegable query).  If they have 20 boxes with blue labels, they will give you the first 10 they find because you can only handle 10 boxes (delegable query with record limit).

If you ask them for all the boxes with blue lamps in them, they tell you - "we can't open the boxes and look", but we can give you the 10 boxes you can carry with you and then you can open them and see (non-delegable query with record limit).  So, you take your 10 boxes and open them to look and find that only 3 of them had blue lamps.  SO...you have 3 boxes with blue lamps - that is your result. 
The problem with a non-delegable query (as you know) is that YES, you got 3 blue lamps and you tell whoever you are getting them for that there are 3 blue lamps...but in reality the store still had a lot of other boxes that might also have blue lamps in them.

 

So, the obvious answer that everyone goes for is - just bump up the record limit to 2000 and cross your fingers.  Well, the real answer is to design your app and data to not only be delegable, but also to limit your records to only the amount you really need in the app.  Because, otherwise you are impacting performance loading up 2000 "boxes" into your truck all the time when you only needed 10 of them.

 

Hopefully that is clear and helpful for you.

 

EDIT: Oh, and again, the way the records come back for Galleries is different as the Gallery "pages" the results differently with the record limits and query.

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

Wow! This should be in the PowerApps documentation! Very clear explanation. Thank you very much.

I tought of a Solution yesterday to keep the information flowing fast, but I am not sure it is a good one for best practice). Surely you can light my way on this one:

 

I have an equipments table as a Sharepoint list that I connect to (700 records so far, but will grow by about a hundred items a year) thus the need for delegation.
When I reach for the SP list to show in a gallery, delegation works because even though my query limit is only 3 (for testing purposes). I get all the items I ask for (filter through a simplet text column). The same thing did not work if trying to store a query into a variable or a collection. I now know why, thanks to your clear explanation 🙂
First challenge seemed settled. The second step was to show distinct equipment (and not all instances of every type of equipment).
With Distinct, delegation did not work (only 3 records returned in the gallery). Since I thought variables and Galleries would not be delegable, I created another Gallery that would fetch the first gallery and only show distinct values of the first Gallery. I thought by hiding that first "reference" gallery, I was being clever. 

It works really well, but I have a feeling that it is not a good practice (hiding a gallery, that is).

 

I would really appreciate your wisdom on this. What would you do in that situation ?

 

By the way, if you ever have some more time later, I would be interested to know how the Galleries function for gathering the information.

RandyHayes
Super User
Super User

@larivibi 

I'll start with the later part - Galleries were designed (IMO) around the fact that people seem to want to show thousands of records in a gallery - because their users really want to scroll through a lot of records to find what they want (sarcasm).  So, this causes issues with performance because not only does the app need to get all the data, but the gallery needs to render it all.  That is a pretty big memory footprint.  So, they made them to page on their own.  They will get a certain number of records first and then as the user scrolls down, continue to get the additional.  This minimized the initial performance issue and the memory issue.  So, they have that little gem in them.  It can be a blessing and a curse depending on how you use the Gallery.

 

For example, using your approach to having a Gallery be a "sub gatherer" in order to do a Distinct on it to get what you want (because yes, Distinct is not delegable).  So, let's say you have 2000 records in your datasource.  If you set the Gallery to that datasource to get the records and then do a Distinct on the AllItems of the Gallery, then you will run into problems because the Gallery will not have loaded all of the records...it has to page them on demand.  How do you demand them...you have to scroll to the bottom until it is no longer gathering new records.  This is problematic because you either have to have the user scroll it, or, if it is hidden, then you need to scroll it by selecting the last record with the Select function (select for a Gallery lets you not only select the gallery, but also a row).  The problem is...you need to specify the row - the last one.  But how do you know what number that is??  Well, you could CountRows on the datasource to get the number of rows - BUT, CountRows is not delegable!!  So, in your case, you would only count rows of 3.

 

The reality is that to do delegation properly and handle situations like this, you really have to think from the data side of things.  If you are using SQL for example, you can offload a lot of the non delegable actions into views.  Example, you can get the distinct in a view and then just get that view in your app (of course with 3 records as your limit, you'll still only get 3 records).  But, based on the above Gallery scenario, you could also have a view that returns the count of all the distinct...so you could select the last row in the gallery and have them all.

 

In the case of SharePoint, you have to plan for these things.  Planning around this is done in a few ways.  One would be to utilize PowerAutomate to create a separate list of all the distinct values.  You could also do it in PowerApps itself, but this is a good job for a flow.  Then, you will have a list with just the distinct values to work from and not need to issue the non-delegable Distinct function.  

How do you get a record count...well, you can't.  But, you can again plan around it with a flow.  If you have another list with even just a single record and a column for each data list that you are interested in and a numeric count of the records in those lists, then you can have flow fill in the current count of records and your app can just refresh that datasource and get the record count.

 

There are a lot of little ways to plan around delegation issues and record limits.  Most of it becomes very specific to the scenario as opposed to "do it like this all the time".  

 

As for the documentation...yes, there is a LOT of details missing in them about these situations.  I think they just left it up to the forum to fill in the blanks 😀

 

Hopefully all clear and helpful for you.

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

Again, thank you for the clear and detailed views you have here!

 

Feeling Enlighted

gjgiraldo
Frequent Visitor

if you use filter for example doesnt depends of the limit in power apps, the limit starts when you use not delegable functions.

another thing , if you save the filter in a collection or global variable , you depends of the limit .

 

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 (5,243)