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.
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 myignite.microsoft.com/videos/53861 (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.
Ralph Boccalini commented
Is there any news about this?
Joe McGiven Corban commented
The last update from Microsoft (above) on this was in June 2018... over 2 years ago! The list threshold is still only 5,000 items, so cross older views ("show items inside folders") will still fail when there are more than 5,000 items in that library. Agree with the original author that this limit is "laughable"... and the fact it's now 5 years since this request, and nothing has happened "now makes me cry" - oh the emotions!
Kevin Still commented
Lookup columns fail for lists with over 5k, very annoying.
Can we get an honest update on this issue?!!
The other problem with Microsoft imposed limits on Lists is users cannot create List templates with content that exceeds a measly 52 MB. So not only are they having to skirt around this 5000 list record limit, but that have additional barriers to creating copies of content just to slim their records down.
We are experiencing issues relating to not having the ability to change permissions or rename folders due to this limitation
Warren Patterson commented
While you at it MS, sort out document libraries lookup fields support for more than 5000 items too. I mean come on, just lazy load the items, its not complex, hire me, I will come do it for you.
Can we have a status update?
Craig Brookhart commented
is there a status on this?
Mohammed Ahmed commented
Limit on files and folder count is a useless option as many user they will keep old data as an archive and in this case user can not share the entire archive.
Toujours aucune solution fonctionnelle depuis toutes ces années, c'est vraiment dommage d'être limité à 5000 items.
Nick Worthy commented
We're using a large list for monitoring Staff Covid status (5000+ staff) and running into performance issues as a result. We have views set up so that users do not load 5000 entries at any time, but there are still odd, intermittent performance problems which MS has ascribed to the size of the list. (see Premier Support ticket: 21802125)
We would strongly support the increase of the limit to e.g. 25k.
I can accept that in the SPOL environment targeting mobile clients to some extent, having a list threshold limit makes sense - for general work with large lists, indexes and filtered views can be used to make it work.
HOWEVER when a lookup field references a large list, you run into the limit and there is no way to work around the issue. Processes that we set up in SP2010 can't be migrated to SPOL!!!
There should be some way to differentiate "allowable values" (Comes from whole list) and Selectable values (Comes from a filtered view) or better filtered with user adjustable query or lookup.
This needs a fix.
I ran into an issue a few days ago due to this 5000 item limit: When creating a View to display files without folders using the Modern interface the View failed. The workaround appears to be to create the View the Classic way:
1. Settings > Library settings
2. Scroll to bottom
3. Click “Create view”. This View works fine.
It would therefore seem that that the 5000 item limit is relatively arbitrary - and is certainly far from ideal. I'd like to add my voice to request that issues such as the above are addressed.
Many thanks :)
Can we get an update from Microsoft on this issue?
Patric Schielke commented
Just to share you guys some insights, why this limit is a real pain in the a..
One of our customers, a big shopping mall, wants to track revenues of all tenants per day. There are about 200 tenants and a year has ~50 weeks with around 6 days that are open. So we talk about 60'000 items/rows entered per year. For every database I know, this is not a problem, but implementing a solution for this in SharePoint it gives you a few headaches. We added folders to the list, for each tenant and year, but still, once you passed a certain limit, you can no longer for example add calculated columns to the list. So, you think its a good tool that won't allow us to make changes after around a year of usage? This means, what could be a cool tool for the job is in reality a not-suitable tool - but maybe the MS guys don't care when we search for a better product elsewhere.
Apparently this is to do with DB row locking. Why it's necessary to lock a row when records are being read rather than written to is not clear. I'm sure it's not easy to change something so fundamental, but they've had 15 years to work on it.
I would almost understand if there were a more premium version of SP they were trying to upsell, with the limit raised - but that doesn't seem to be the case. I hope competitors such as Alfresco reach feature parity quickly with features like lookups and web part connections, so that large organisations can ditch this legacy mess.
When is this going to be implemented?!! This is causing massive problems in our tenant. We are having to break up large lists that were in our on-premise environments into multiple lists. Not ideal! This is creating all kinds of extra work for IT and business users. Large global companies can't be limited to 5,000 records.
Maybe we all need to start emailing Jeff Teper.
This is now having a significant impact on our site functionality.
So 2 years no update. Please give us feedback. We need that soon.
I had today an case where i needed to share a folder with ~1500 Subolders and multipe subfolder structures and in total 132.000 files to other users. I wasn able to do that. Kinda frustration. I got theese files from box.com and box.com was able to share that amount of data.