1. Do you get the Yellow Triangle (delegation warning)?
2. Usually the limit is 500. Did you change the limit to 2000?
3. The limit does not apply unless you are using query that does not support delegation to the data source. That means PowerApps is doing the work itself instead of using the data source, so PowerApps has to impose a limit on those types of queries. Do you get the Yellow Triangle warning? Check by clicking the Stethoscope Icon (App Checker).
4. How to get rid of the warning - this depends on your specific case - first, do you get the warning?
Thank you so much for this traditional paging logic.
I had a scneario where I needed to use this with SharePoint list datasource. It doesnt work with it. Do you have any idea or alternative for SharePoint list?
I need to use one of the non-delegable operator In while fetching data from large sharepoint list. But it doesn't work as expected because of delegation. Could you please show some pointers?
I start with an approach of using the right data source for the right job. If your data needs are very heavy, then your data should reside in SQL, CDS, or something on the same level. These connectors support more delegable queries like the in operator.
If the data needs of a problem you are solving are simpler, then you can work within the boundaries of the SharePoint connector, which can be browsed with StartsWith and EndsWith today.
Hi @Mr-Dang-MSFT ,
I appreciate your input. Our dataset is around 4000 records or less and our source would have to be from Excel. Would your recommended approach using Flow work?
Check it out!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020