Power Apps canvas apps: set the data row limit to 10,000
Canvas app makers can raise the data row limit to 10,000, but larger local queries can affect performance and do not replace delegation.
Key insights
- In Power Apps Studio, find the setting under Settings > General > Data row limit.
- The demonstration shows a Dataverse ClearCollect returning 10,000 rows with the setting raised.
- The SharePoint test errors on the first 10,000-row request; changing the setting to 5,000 and back changes the observed behavior.
- Power Apps displays a warning that fetching and processing too much data can significantly degrade performance.
- The 10,000 setting does not make every query complete: nondelegable formulas still work only with the rows retrieved locally.
Power Apps canvas apps can raise the Data row limit to 10,000 records, giving nondelegable formulas a larger set of records to process locally. This matters to makers maintaining apps that rely on local processing, but it does not make every query complete or remove the need for delegation. Ronan Vico Technologies demonstrates the setting and tests it with SharePoint and Dataverse data sources.
What's new
The app-level Data row limit can now be configured as high as 10,000, rather than the historical 2,000-record maximum described in the source material. The setting determines how many records a nondelegable query can retrieve for local processing; it does not change how many records exist in the connected data source. It also is not a universal cap on every operation in a canvas app.
Delegation is the alternative that matters for scale. With a delegable formula, Power Apps can send supported filtering or other operations to the connected data source, which processes the query before returning results. A nondelegable formula instead works over a limited set of rows retrieved to the app. Raising that limit expands the local working set, but records outside it can still be missed.
Power Apps warns in Studio when the value is raised above 2,000: “Fetching and processing too much data can significantly degrade performance.” That warning reflects a practical trade-off. Retrieving a larger set can mean more data transfer and local processing, so a higher limit is not automatically a better setting.
Who it is for and what you need
The change is relevant to canvas app makers who have a specific formula or connector scenario that cannot be delegated and need more than the default local result set. The setting is configured for the app, so changing it may affect multiple nondelegable formulas. The material does not identify a required Power Apps license, plan, or admin role.
The demonstration describes the setting as rolling out and notes that it may not yet appear in every environment. It does not establish a rollout schedule, regional scope, or a universal availability date. Check the app’s settings in Power Apps Studio rather than assuming the option is present in every environment.
Before increasing the limit, identify whether the formula is delegable and whether the app genuinely needs a larger local dataset. The research material recommends keeping the limit as low as practical and treating delegation warnings as potential correctness issues: a formula that only examines a subset of a data source may produce incomplete results.
How it works
- Open the canvas app in Power Apps Studio and select Settings.
- Open General and locate Data row limit.
- Set the value between 1 and 10,000. The demonstration shows a performance warning when the value is higher than 2,000.
- Test the formulas and data sources used by the app. Compare the returned records with the expected result, and watch for delegation warnings or performance changes.
In the demonstration, a button runs ClearCollect to load records into a collection, and a label uses CountRows to display the collection size. With Dataverse and the limit set to 10,000, the test returns 10,000 rows. That is an example from one test, not a guarantee that every connector or formula will return that many.
The SharePoint test behaves differently. The initial request attempts to retrieve 10,000 rows and fails in the demonstrated setup. The presenter attributes this behavior to SharePoint’s 5,000-item threshold and shows Power Apps Monitor recording a Get Rows request. After changing the setting to 5,000 and then returning it to 10,000, the observed requests include Get More Rows and a skip token, indicating pagination in that test.
Monitor can help makers inspect those requests and see whether more rows are being requested. The transcript reports that this sequence worked in the tested app, but does not establish that changing the setting back and forth is a supported or dependable fix. Treat it as an observation to verify in your own environment, not as a general workaround.
Limitations and open questions
The 10,000-row setting is not a substitute for delegation, and it does not guarantee complete results from a larger data source. For nondelegable formulas, relevant records beyond the local limit can be excluded. Connector support also differs, so a result from Dataverse should not be assumed to predict the behavior of SharePoint, Excel, or another source.
More local data can increase transfer, memory, and formula-processing demands. The video specifically warns makers to consider the effect of collecting thousands of records, particularly for mobile use. Avoid loading a complete remote table into a collection unless the app needs it and the expected cost has been tested.
The SharePoint behavior remains unresolved in the supplied material: the presenter calls it a bug and says they intend to ask Microsoft about it. No official Microsoft source was provided here to verify that diagnosis, confirm a fix, or establish rollout details. For larger workloads, the research material recommends delegation-first designs, early filtering, and testing against realistic data volumes.
Sources
Frequently asked questions
How do I set the Power Apps canvas data row limit to 10,000?
In Power Apps Studio, open Settings, select General, and set Data row limit to a value up to 10,000. The option may not yet appear in every environment, according to the demonstration.
Does a 10,000 data row limit make a nondelegable query complete?
No. It expands the number of records available for local processing, but records beyond the configured limit may still be missed. Delegation remains the preferred approach for queries over larger data sources.
Does the 10,000-row setting work with SharePoint?
The demonstration’s initial SharePoint request for 10,000 rows fails, while changing the setting to 5,000 and back produces a paginated request in that test. The material does not verify a general fix or confirm the cause.
What happens to performance when I raise the data row limit?
Power Apps warns that fetching and processing too much data can significantly degrade performance. The research material also notes that larger local datasets can increase download time, memory use, and processing time.