cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
twister
Post Partisan
Post Partisan

dropdown got delegation warning

Hi, How do I solved this warning on dropdown selection? My record only got 700++ and I have already set the limit to 2000

 

twister_0-1620029136438.png

 

twister_1-1620029159885.png

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
RusselThomas
Community Champion
Community Champion

Hi @twister ,

It's just a warning - you will always get it when you increase the default data row limit size.  You can choose to ignore it, but you should know the implications of doing so.  You won't get rid of the warning unless you set your limit back down to 500.

 

The intent behind this setting is to limit and minimize data transfer wherever possible - apps, especially mobile apps, are not supposed to be transferring huge amounts of data around.   Imagine you run the equivalent of a "Select * from" against a SQL table that contains terabytes of data from a mobile device?  Not ideal.  

Mobile Apps (and in fact, most apps) should be very picky about the data they transfer, and should always aim to be highly performant and optimised from a data perspective, only fetching what is required.  PowerApps especially is a connection-based tool - it does not (primarily) store data in the app, but relies on data stored in data sources - therefore, traffic between the app and the source is of primary concern.

 

Optimisation is usually achieved by building queries that support filtering and refining data at the source so that your app just receives the data it needs for your user to consume/interact with.  These queries are effectively "delegated" to and executed by the source.

Queries (or sources) that don't support delegation behave differently and this behaviour can negatively impact your user experience dramatically.

There are two key problems that arise with non-delegable queries or sources;

  1. Accuracy
  2. Performance

To try and illustrate this, let's assume you're applying some sort of filter query to a SPO list that has 10 000 rows in it.  Based on your filter, you're expecting 10 rows to come back from your query.

The 10 rows you're looking for are sitting inside your 10 000 row dataset as follows;

  • 1 is found within the first 500 rows of the 10 000
  • 4 are sitting somewhere between row 501 and row 2000 
  • 4 are sitting somewhere between row 2001 and row 6000 
  • 1 row in sitting somewhere between row 6001 and 10 000

Consider this delegable example with a data row limit of 500;

  1. You run a query to SPO using a delegable filter function.
  2. PowerApps sends the query to SPO
  3. SPO runs the filter on the entire dataset of 10 000 rows and only returns your 10 rows of data that match the filter. 

10 rows are returned from the query.  This is the correct result and the one you want.

 

When you send a non-delegable query from Power Apps to the source, PowerApps replaces it with the equivalent of

FirstN(yourDataSource, n)

where 'n' is your configured 'data row limit'.

The source will therefore just dump/return the first n rows.  No filters and no refinement get applied when this happens, so you will just get the first 500 rows of your data. 

PowerApps will then apply your original non-delegable query against that subset of data now sitting in your app session. 

This means you would be pulling more data than you need, potentially slowing down the user experience and (for mobile devices) incurring unnecessary data costs, and on top of this you could be getting inaccurate results because your query is being run against an incomplete data set. 

 

Consider the same example as above with a non-delegable query;

  1. Same SPO list with 10 000 rows in it.
  2. You run a query to SPO using a function that is non-delegable, but you still expect the same 10 results to come back.
  3. PowerApps asks SPO for the first 500 rows of data.
  4. PowerApps then applies your expression to the 500 row dataset that was returned and finds 1 result.

So instead of finding 10 results from the full 10 000 checked, you're now only getting 1 result from the first 500 checked.  On top of this, instead of just getting 10 rows back from SPO, PowerApps is getting 500 rows, and still returning an inaccurate result.

 

Consider the non-delegable response if you increase your row limit to the max, 2000.

  1. SPO still ignores the filter expression and returns the first 2000 rows of data.
  2. PowerApps then runs your filter expression on the dataset that was returned and displays 5 results instead of 10.

Once again, instead of just getting 10 rows back from SPO, PowerApps has to get 2000, and then it still doesn't provide you with an accurate result because there are only 5 rows matching your query within the first 2000 rows of your data.

 

The intention with data row limits and being able to increase them is not so you can suck in bigger datasets to run non-delegable queries against - it's there mostly to increase the size limit of valid data returned - i.e. something that your source has already filtered (so let's say instead of 10 results, you were expecting to find 600 - PowerApps would have capped the returning result at 500 thanks to the data row limit - increasing it can resolve this issue).  Increasing this can still slow down your app though - hence the warning, so do it with care.

 

Kind regards,

RT

View solution in original post

4 REPLIES 4
RusselThomas
Community Champion
Community Champion

Hi @twister ,

Dropdowns and ComboBoxes work differently in terms of how they query the source.  ComboBoxes have an additional "Search" capability, so the actual query going to the source is a Search() function.

This means, you will always get the Delegation warning with ComboBoxes that have search enabled for sources that don't support Search() as a delegated function.  If you don't need the "Find Items" capability of a combobox, then you can disable this by setting the IsSearchable: property to false and you should see the delegation warning disappear - if you do need it however, then you will be stuck with the delegation limitation (on a ComboBox anyway).

The other alternative is to use a dropdown, or build your own "dropdown" using a text input and a small gallery, but instead of being tied to the builtin Search() of a combobox, you can instead use the Filter() function.

Kind regards,

RT

twister
Post Partisan
Post Partisan

thanks for info but I also got delegate warning on App maybe due to deep linking function? What is the problem exactly? I have no idea on this warning..

 

twister_1-1620040396596.png

 

 

twister_0-1620040373160.png

 

twister_2-1620040461884.png

 

RusselThomas
Community Champion
Community Champion

Hi @twister ,

It's just a warning - you will always get it when you increase the default data row limit size.  You can choose to ignore it, but you should know the implications of doing so.  You won't get rid of the warning unless you set your limit back down to 500.

 

The intent behind this setting is to limit and minimize data transfer wherever possible - apps, especially mobile apps, are not supposed to be transferring huge amounts of data around.   Imagine you run the equivalent of a "Select * from" against a SQL table that contains terabytes of data from a mobile device?  Not ideal.  

Mobile Apps (and in fact, most apps) should be very picky about the data they transfer, and should always aim to be highly performant and optimised from a data perspective, only fetching what is required.  PowerApps especially is a connection-based tool - it does not (primarily) store data in the app, but relies on data stored in data sources - therefore, traffic between the app and the source is of primary concern.

 

Optimisation is usually achieved by building queries that support filtering and refining data at the source so that your app just receives the data it needs for your user to consume/interact with.  These queries are effectively "delegated" to and executed by the source.

Queries (or sources) that don't support delegation behave differently and this behaviour can negatively impact your user experience dramatically.

There are two key problems that arise with non-delegable queries or sources;

  1. Accuracy
  2. Performance

To try and illustrate this, let's assume you're applying some sort of filter query to a SPO list that has 10 000 rows in it.  Based on your filter, you're expecting 10 rows to come back from your query.

The 10 rows you're looking for are sitting inside your 10 000 row dataset as follows;

  • 1 is found within the first 500 rows of the 10 000
  • 4 are sitting somewhere between row 501 and row 2000 
  • 4 are sitting somewhere between row 2001 and row 6000 
  • 1 row in sitting somewhere between row 6001 and 10 000

Consider this delegable example with a data row limit of 500;

  1. You run a query to SPO using a delegable filter function.
  2. PowerApps sends the query to SPO
  3. SPO runs the filter on the entire dataset of 10 000 rows and only returns your 10 rows of data that match the filter. 

10 rows are returned from the query.  This is the correct result and the one you want.

 

When you send a non-delegable query from Power Apps to the source, PowerApps replaces it with the equivalent of

FirstN(yourDataSource, n)

where 'n' is your configured 'data row limit'.

The source will therefore just dump/return the first n rows.  No filters and no refinement get applied when this happens, so you will just get the first 500 rows of your data. 

PowerApps will then apply your original non-delegable query against that subset of data now sitting in your app session. 

This means you would be pulling more data than you need, potentially slowing down the user experience and (for mobile devices) incurring unnecessary data costs, and on top of this you could be getting inaccurate results because your query is being run against an incomplete data set. 

 

Consider the same example as above with a non-delegable query;

  1. Same SPO list with 10 000 rows in it.
  2. You run a query to SPO using a function that is non-delegable, but you still expect the same 10 results to come back.
  3. PowerApps asks SPO for the first 500 rows of data.
  4. PowerApps then applies your expression to the 500 row dataset that was returned and finds 1 result.

So instead of finding 10 results from the full 10 000 checked, you're now only getting 1 result from the first 500 checked.  On top of this, instead of just getting 10 rows back from SPO, PowerApps is getting 500 rows, and still returning an inaccurate result.

 

Consider the non-delegable response if you increase your row limit to the max, 2000.

  1. SPO still ignores the filter expression and returns the first 2000 rows of data.
  2. PowerApps then runs your filter expression on the dataset that was returned and displays 5 results instead of 10.

Once again, instead of just getting 10 rows back from SPO, PowerApps has to get 2000, and then it still doesn't provide you with an accurate result because there are only 5 rows matching your query within the first 2000 rows of your data.

 

The intention with data row limits and being able to increase them is not so you can suck in bigger datasets to run non-delegable queries against - it's there mostly to increase the size limit of valid data returned - i.e. something that your source has already filtered (so let's say instead of 10 results, you were expecting to find 600 - PowerApps would have capped the returning result at 500 thanks to the data row limit - increasing it can resolve this issue).  Increasing this can still slow down your app though - hence the warning, so do it with care.

 

Kind regards,

RT

twister
Post Partisan
Post Partisan

very nice of info with example..very2 clear and appreciate it..

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,511)