Answered

unable to process more than 2000 records, causing issues with cascading filters.

(0) Share

Report

Posted on by RJ-25050706-0

Cascading filters in Power Apps forms built on SharePoint lists are not functioning as expected because the application cannot read beyond the 2000-record delegation limit.

Issue.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Kushal_M 296 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello RJ-25050706-0,

This is a common limitation when building cascading filters in Power Apps over large SharePoint lists. The issue is not the dropdown logic itself — it is caused by delegation limits in SharePoint connectors. Because SharePoint is non-delegable for several filter/search operations, Power Apps only processes the first: 500 records (default), 2000 records (maximum configurable limit). After that, cascading dropdowns and gallery filters start behaving inconsistently.

Your form appears to use cascading filters like:

Typical formulas like:

Distinct(
Filter(
InvoiceList,
BusinessUnit = ddBusinessUnit.Selected.Value
),
ClientName
)

work only on the first 2000 records if the query becomes non-delegable.

Use Delegable Filters Only (Recommended for SharePoint). You must ensure every filter is delegable like

Filter(
InvoiceList,
BusinessUnit = ddBusinessUnit.Selected.Value
)

Non-Delegable:

Search()
Distinct()
In
LookUp inside Filter
StartsWith on complex columns.

Another option is to Move Data to Dataverse (Best Solution). If possible, migrate the SharePoint list to Microsoft Dataverse. Dataverse supports Delegation on large datasets, Relational tables, Proper indexing, Better cascading filters, Security roles, Scalable Power Apps apps. This is the enterprise-grade fix.

Was this reply helpful? Yes No
BCBuizer 22,833 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @RJ-25050706-0,

Can you please share the formulas you are using for the Items properties of the various dropdown controls? Also, please share the type of the column that are involved. Based on this, perhaps a workaround can be found that will enhance the performance to an acceptable level.

If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.

Was this reply helpful? Yes No
Suggested answer

WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @RJ-25050706-0,

I have some blogs on Delegation - the second one in particular may be of use to you grouping the Delegable queries inside a With() statement then the non-delegable ones processed locally. As long as you can get the top filter to return under 2,000 records (the list can be of any size), any valid queries will then work on the second filter with no Delegation limitations. I have used this process on large (100k +) SharePoint Lists in prod apps fopr many years.

It would look something like
With( { _Data: Filter( SPList, YourDelegableFiltersHere ) }, Filter( _Data, YourNonDelegableFiltersHere ) )

Happy to expand further if you provide your filter code (your attached file cannot be opened).

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @RJ-25050706-0,

A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No