Feedback by UserVoice

I suggest you ....

Remove the list view threshold (5000 by default)

This limit has always been a bit laughable, and is even more so as we develop more client side applications. In SharePoint 2007 we didn't have this limit and were allowed to make our own mistakes. Now that hardware is so much more powerful, we need this limit removed so that we can build enterprise-class applications.

1,419 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

sympmarc shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We are continuing to make our large list experiences better, please keep the feedback coming.

Spring 2018 update:
- We now support being able to manually add indexes to lists of any size (increased from lists up to 20,000 items previously).
- Starting with the February release of the Office 365 Excel client, you will be able to export your full list instead of getting cut off part of the way through.

What we are working on now:
- Predictive indexing will start to work for lists larger than 20,000 items so your views will automatically cause the right indexes to be added to your lists.

In our backlog:
- Being able to index/sort/filter by lookup column types (like person, lookup or managed metadata columns) without being throttled.
- Making sure that our REST APIs support querying in ways that will guarantee that the call will not be throttled.

For a general update on large list capabiltiies, the video on (focusing on large lists at 42 minutes and 25 seconds) describes some of the changes that we delivered back in the second half of 2017:
- Modern UI now has a lot of support for adding indexes to large lists and libraries on the fly, reducing the number of throttling errors experienced by our users, and some new UI for browsing through items in large lists with our paging model
- SharePoint runs predictive indexing jobs to automatically add indexes as lists get larger based on your view definitions, and updates these indexes when you add/update your views

Looking forward to receiving more of your feedback.


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Guillaume OBSER commented  ·   ·  Flag as inappropriate

    I plan to abandon Sharepoint in 2017, SharePoint is became to complcated to maintain due to this limit. Using sharepoint was a mistake and this application is clearly the stepchild of the Office 365 tools.

  • Eric Alexander commented  ·   ·  Flag as inappropriate

    No matter how much you preplan for large lists, something always changes down the line and you become powerless to do anything about it. Users can keep adding, and adding, and adding, and you as an administrator have NO means to help them. Moving or deleting files to get under 5000 items causes a whole range of problems; it's clumsy, slow, difficult, time consuming, and can lead to 404s as people try to access content that has been moved. Increase the limit, give us a happy hour, or update TechNet to show the actual boundary of SharePoint Online to be 5,000 items, not 30 million.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a big show stopper every time we want to convert a team from using Excel, FileMaker Pro or Access to a SP site with multiple lists and look ups.

  • Tans commented  ·   ·  Flag as inappropriate

    I cannot believe that anyone would scroll through 5,000+ list items (& documents), BUT we do need to be able to easily filter a 5,000+ lists and/or retrieve calculations on the results of 5,000+ so is a possible solution.....

    Provide with every list a filter/refiner web part that appears above the list if switched on lets say in the view settings. The web part could auto show the fields that have been set in the view settings, so users can select from option fields, select dates, etc...The list on open can either show no data or the first 'x' number of results based on the view and a message informing the user that only 'x' is being shown. If the refine/search results is over 5,000+ show the max amount but provide any count/sum set in the view. Just putting it out there (maybe someone below has !).

  • Anonymous commented  ·   ·  Flag as inappropriate

    Since other online storage services don't have this problem, it's pretty clear it's caused by the way SP gets data from the db. SP is an antiquated server based platform probably not well suited to online use in its current form. The idea that SP has to request all items in a list to return a filtered view of say 25 items is absurd. The filtering should happen before the request gets sent but SP simply doesn't work that way and until it's modernized (or in typical Msft fashion, replaced), it's not fit for enterprise use.

  • Sam commented  ·   ·  Flag as inappropriate

    The 5,000 file limit is a massive problem for small business users of Office 365. Those wanting to move to a one-stop modern Office/Email/File management system face unreasonable restrictions due to this limit. While SharePoint is powerful and does make overcoming this limit possible with customized list views, most small businesses aren't going to take the time to administer SharePoint sites. Instead they're stuck paying the monthly subscription fee for Office 365 and paying more for a Dropbox or Box licence.

    You have to fix this and make the SharePoint/OneDrive for business services more appealing for those wishing to migrate from Dropbox or Box.

  • TechAdmin commented  ·   ·  Flag as inappropriate

    Please make searching for items in document libraries with more than 5000 items work.

    If a search query is triggered from within the document library, and the query pulls back a large number of results - clicking the 'See more results' link shows no items at all. A really poor experience and confusing for end users.

  • Franchesca V Havas commented  ·   ·  Flag as inappropriate

    I agree that this limit needs to be raised. As a SharePoint developer from the 2001 database beta version we used in Texas to today I can say that this is by far one of the top 10 problems we are encountering today.
    Please raise the view limit!

  • Marc Wenning commented  ·   ·  Flag as inappropriate

    this limit really needs to raised, 5,000 items is way to low. Needs to be somewhere in the 40-50,000 item limit range for sharepoint online. Please raise the view limit!!!

  • Andy Dale commented  ·   ·  Flag as inappropriate

    The 5000 limit causes me endless problems. I keep creating and changing views, have all key columns indexed but still get call from irate customer every few months saying 'Threshold Limit has been reached'. The issue is that to pull all items back on an individual (patient) we have a link that searches all the items in the list. Please, please find a way to fix this biggest frustration.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This limits creates a ton of confusion for IT and end users. Our customer thinks their data is missing. 5,000 item limit is simply way too low, especially when SharePoint lists is seen as a replacement for databases in certain cases. You HAVE to come up with something better...

  • Anonymous commented  ·   ·  Flag as inappropriate

    Within our 400 person organization, I'm the only IT resource to keep everything IT running. File shares are easy to maintain - they just work. This limitation on views effectively prevents us moving file shares to SharePoint as I lose the ability to edit permissions when there are more than 5000 items in a library - that's after breaking down 8 main shares into over 50 libraries to try and get around this limit.
    I wasted many hours zipping and shuffling data around only to find users had once again gone over 5000 items afte a few weeks. It's too hard to maintain.

  • Pascal van Alphen commented  ·   ·  Flag as inappropriate

    Hi SharePoint Team,
    I'm sorry but that line of thinking doesn't sound reasonable to me. I agree that there are definitely situations in which you can work around the issue using appropriate views or indexes, but there are simply too many common business scenarios in which this is not possible.

    What if the most important business information around a customer's documents - the fields you really want to filter on - are multi-value lookups? In that case you get no index option, no filter option, so in essence your existing most important library views become useless.
    Limiting the view based on something like a start and end date is often not a workable solution.

    Then there is the issue where you need to query your entire list based on certain criteria. I've run into this problem not only in views but also in some selections done from workflows. As a UI limit I can fully understand a 5000 limit, but for a selection in the background?

    Please understand that this is truly a deal-breaker for several of the customers that I work for. If you seriously want to keep talking about SharePoint as providing 'enterprise grade' solutions (quote from the Future of SharePoint event on May 4th, 2016) then you simply have to get rid of this limitation.

  • Sol Birnbaum commented  ·   ·  Flag as inappropriate

    Hello SharePoint Team, we have lists over 5000 items, but they are distributed across around 100 root sub-folder. This works great as far as responsiveness, HOWEVER the new library look refuses to open the library (it open in old look). While this is still in preview, please can you allow 5000+ item in new view, provided they are being managed correctly? We are an MSP and our clients have similarly size and well structured shares. We won't be able migrate them to SharePoint with this limitation and will need to explore other EFSS options; we would prefer to stay with SharePoint though.

  • David Shumate commented  ·   ·  Flag as inappropriate

    I agree with all of the comments here. I believe that while this limitation exists, and the end users I support expect to be able to use the Windows Explorer view (which works sometimes and other times not) to access a document library with greater than 5000 items, that the "Open with Explorer" ribbon menu item should be disabled since the behavior is uncertain. My end users do not care to learn technical details about an issue and are not interested in descriptions of the same technical issue as a response to there questions about why it is not working. To me, if it isn't functioning 100% than it should be disabled when the condition exists for which it may not work, and to that end, maybe it will put a little fire under the issue to get it moving. This has been a problem for a long time based upon my reviews of technical articles going back years, and given the present strategy for Microsoft's cloud vision, would seem to be a self imposed barrier to making that vision a reality. Please address this issue asap!

Feedback and Knowledge Base