web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Power Apps data limita...
Power Apps
Suggested Answer

Power Apps data limitation

(1) ShareShare
ReportReport
Posted on by 16
I have a SharePoint list that is being used as a data source for Power Apps. I noticed that there is a limitation on how much rows of data can be shown on the app - 2000. Is there any work around with this?
Screenshot 2026-04-14 090058.png
Categories:
I have the same question (0)
  • Suggested answer
    Pstork1 Profile Picture
    69,417 Most Valuable Professional on at
    That limit is the number of rows that can be returned by any connector in one call.  It is not a limit on how many rows can be displayed in the app.  There is no way to change that limit. But, when working with a local collection the only limit on the number of rows is the amount or RAM you have in your device.  Having said that, using large local collections to hold data is not a good idea. It can cause performance problems and since it is separated from the actual data source it can also lead to bad data if more than one person is accessing the data.  A better approach is to use delegable functions to pre-filter the data being used in the app at the data source. That way your user has access to all the data, but only works on a smaller subset of data at any one time.  That kind of design is better for performance and preserves data integrity better.

    ----------------------------------------------------------------------------------
    If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

    Paul Papanek Stork, MVP
    Blog: https://www.dontpapanic.com/blog
     
  • Suggested answer
    Vish WR Profile Picture
    2,823 on at
    @SP-08081250-0

    The 2000-row limit exists because of delegation.

    Power Apps is designed to avoid loading large datasets into the app, which would slow performance or even crash it. So instead:

    - It tries to delegate (send) the query to SharePoint  

    - SharePoint processes the data and returns only the results  

    Workarounds

    - Use **delegable functions** (`Filter`, `Sort`, `LookUp`)

    - Filter data early** (don’t load full list)

    - Use **indexed columns** in SharePoint

    - Implement **pagination / load in chunks**

     

     Key Point

    Don’t try to load everything — **filter + delegate is the best approach**.

     
     
      Vishnu WR
     
    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 â™¥
     
     
     
  • JeovanyVelasco Profile Picture
    4 on at

    The 2000 limit is real, but it’s not really the problem — it’s just how Power Apps handles non-delegable queries. What actually matters is why you need more than 2000 rows and how you plan to use them.

    If you truly need more (e.g. ~3000 rows), you can split the load into chunks and merge locally. For example: load multiple filtered collections (3 batches of 1000) and combine them in App OnStart. This works, but has trade-offs: slower initial load, higher memory usage, and risk of stale data in multi-user scenarios.

    If the dataset is larger or dynamic, this doesn’t scale well. Better approaches are: use delegation (filter at source), implement pagination, or use Power Automate to return controlled datasets.

    From experience, most cases don’t actually need thousands of rows at once — it’s usually a design issue. If you can share how you plan to use the data (not just how much), there are better patterns depending on the scenario.

  • Suggested answer
    11manish Profile Picture
    2,286 on at
    The 2000 limit:
    • Is a query/connector limit, not display limit
    • Cannot be increased
    Best solution:
    • Use delegable functions
    • Avoid large collections
    • Filter data at source
  • WarrenBelz Profile Picture
    155,279 Most Valuable Professional on at
    I have a number of blogs on Delegation - the first two in particular may be useful to you for your query.
     
    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  
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 1,074

#2
Valantis Profile Picture

Valantis 639

#3
11manish Profile Picture

11manish 606

Last 30 days Overall leaderboard