Answered

Suggestions for managing the 2000 item limit in Power Apps

(1) Share

Report

Posted on by CU15052342-0

Hello,

I am creating an app to track action items and their associated tasks. SharePoint lists are the backend. The app's home screen is a gallery of all Action items. If there are roughly 260 working days per year and at least 3 action items per day, it will be a little over 2 years before I hit the 2000 limit Power Apps limit. What should I consider in the design, today, to ensure the app will continue to work in the years ahead. The client wants to be able to see all of the Action items in a dashboard that I plan on setting up in Power BI so leaving them all in the Action Item list is desirable although I have considered archiving off completed action items into another list.

Some columns I have in the action items are due date, priority, status, and assignee.

Currently I have a filter combo box assigned to each field in the gallery as well as sort for each field in the gallery.

Looking even further out, what about the SharePoint 5000 item view limit does that impact the depth that the filter's can go. I am familiar with deligation I am just not sure I've seen or read anything about techniques for power apps and large datasets.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Verified answer

Kushal_M 296 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello CU15052342-0 ,

You are thinking about the right problems early.

A Power Apps + SharePoint design can absolutely scale well beyond a few thousand records, but only if you design for delegation, indexing, and query patterns from day one. The SharePoint 5,000 items threshold is is not a SharePoint storage limit, its a view threshold. The real issue is whether your app uses delegable queries and indexed columns. Your projected volume is actually fairly modest:

3 action items/day
~260 workdays/year
~780/year
~1,560 after 2 years
~7,800 after 10 years

SharePoint lists can comfortably handle this if designed correctly.

My Recommendation for Your Specific App

Keep One Main List, Add Indexes Immediately, especially:

Status

DueDate

Assignee

Priority

Ensure All Gallery Queries Delegate, Avoid Search() and Use

StartsWith()

dropdown filters

metadata filters

Add an IsActive Column for future-proofing for archive logic.

Plan for Archiving Later Likely around 10k–20k items or when performance degrades Keep Power BI Separate. Power BI can unify:

active

archived

historical

with no user impact.

Your projected scale is very manageable if you build with delegation and indexing discipline from the beginning.

🏷️ Please tag me @Kushal_M, if you still have any queries related to the solution or issue persists.

❤️ Please consider giving it a Like, If the approach was useful in other ways.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.

Was this reply helpful? Yes No
Verified answer

WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @CU15052342-0,

I have a number of blogs on Delegation - the first two in particular may be useful to you - the two "limits" only relate to

2,000 is the maximum you can set your local Data Row Limit to and only imposes some restrictions on non-Delegable filters and some "local" functions. There are many ways to manage larger lists, in particular Delegable queries, but also pre-filtering as per this blog.

5,000 is the limit on some SharePoint views (from the SharePoint interface). The effect it has on Power Apps (and SharePoint) is that you need to index (in SharePoint) any columns that you are using for queries. Your are allowed 20 indexed columns per list.

I have been using almost exclusively SharePoint for over 8 years and have several customers with SharePoint lists over 100,000 records - I am yet to find anything I could not satisfactorily manage.

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
Suggested answer

Vish WR 3,748 on at

Like
a
(2)

Report
Copy link

Link copied!
@CU15052342-0

The 2000 limit is just the max for your app's local Data Row Limit setting. It doesn't mean SharePoint stops working at 2000 items. As long as your gallery uses delegable queries, Power Apps fetches from SharePoint server-side and the limit becomes irrelevant. The problem only kicks in when you use non-delegable functions like Search() or CountIf() — those only operate on the local 2000 rows, not the full list.

What to do right now in your design:

Index your key columns immediately — Status, DueDate, Assignee, Priority. These are exactly the columns you're filtering on, and SharePoint needs them indexed to handle queries efficiently beyond 5000 items. You can do this in List Settings → Indexed Columns.

Replace Search() with StartsWith() or Filter() with indexed columns — Search() is not delegable to SharePoint. If your combo box filters use Search, swap them out now before the habit is baked in.

Avoid filtering on calculated columns or Person fields with complex expressions — these can break delegation silently and only affect you once you exceed the local row limit.

On the 5000 SharePoint view threshold

This only impacts SharePoint list views in the browser, not Power Apps directly — as long as your Power Apps queries hit indexed columns. The real rule is: if the column is indexed, your Filter/SortByColumns calls stay delegable and won't be blocked, regardless of list size.

Your Power BI plan is the right call — keep everything in one list, let Power BI handle the full historical dashboard, and only add archiving if performance actually degrades (realistically not until you're well past 50k+ items for a simple action tracker).

You're thinking about this at the right time — the design decisions you make now will save a lot of pain later!

Vishnu WR

LinkedIn - My Tech Space

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 ♥

Was this reply helpful? Yes No