Analogy
Imagine reading a book where only the first few pages are visible and the rest are locked. You think you’ve read the whole story — but most of it is missing.
Explanation
- Power Apps has a row limit for non-delegable queries (default 500, maximum 2,000).
- When this limit is reached, Power Apps stops retrieving additional records.
- Any filter, search, or calculation runs only on the loaded rows.
- As a result, some data may be missing from the app view.
- Users may not realize that the dataset is incomplete.
Example
Suppose your app connects to a SharePoint list containing 20,000 records. If the query is non-delegable, Power Apps might load only the first 2,000 records. When a user searches for a value that exists beyond those 2,000 rows, the app may incorrectly show “No records found.”
Key Takeaway
When Power Apps hits the row limit, it does not show an error. Instead, it silently works with partial data — which can lead to inaccurate results.
