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.
Tom Turpin commented
Last Admin Response: June 08, 2018...
Wow... Just wow. I am working with a state level department with over 500,000 files in one network share alone. SharePoint Migration let me migrate the files, but now I'm told to find the folder with more than 5,000 items and split it so that I can "Fix" the inheritance issue.
Clearly a large problem for many...
Will this fix the Onenote clipper list limit so the clipper can find my folders?
This limitation as well as the similar one "When a list, library, or folder contains more than 100,000 items, you can't break permissions inheritance on the list, library, or folder. Nor can you re-inherit permissions on it. " has caused us to halt a massive migration for many thousands of users from Box to SharePoint online. The limits show that we can store up to 30 million files and folders in a document library, however this is INCREDIBLY misleading because if you store more than 100,000 items, then you can never break inheritance on a folder and set unique permissions. MS needs to fix this or change their documentation to not falsely lead users that it can support 30million files per document library, but if you store more than 5,000 you cannot share a folder, and if you store more than 100k you can not use unique permissions.
PLEASE CHANGE THIS!!!!!!!!!!!!!
Jason Teh commented
we need to have this threshold removed. this limitation really jeopardized the whole purpose of SharePoint at the enterprise level.
Where are we with this?
"SharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded · June 08, 2018"
Seems like maybe time for an update? This is a real-world issue. The executives buying your product are feeling the bait-and-switch when they go to try to leverage the tool then find out they need to go buy Dropbox or Box.com for their users and have a fragmented experience.
Matt Gudites commented
Just fix this already!!!
We need to export more than 1000 item from a filtered view, this issue is problematic. Our end users depend on exported data to create their reports & analysis of data.
Appreciate if this can be solved ASAP
Warren Anonymous commented
"sympmarc shared this idea · Jun 17, 2015"
My maths isn't good, but i'm sure we are nearing 6 years since this was asked on this specific UserVoice, I know there are other UserVoice's asking the same thing, I think if MS took the vote count from all the splintered versions of this request, it would be the most requested feature. But I think the problem isn't the fact it cant be done, its more an issue with server performance, I don't think this will ever be done now especially with more people jumping onto office365, this probably falls further down the line of things to do.
This limit also has an impact on changing permissions on files, folders, directories, moving files, restore from recycle bin in sharepoint powershell. None of this can be done because of that limit and this should be explained in your documentation so at least we know and not discover this huge problem after migrating an on prem file server shares to sharepoint/onedrive and look like idiots to clients.
Zain Hassan commented
I'm pretty sure this will still be an issue by the time I die. Microsoft is really failing us here. It's 2021 come on lol, just because you guys don't want to invest resource into this doesn't mean it's not essential.
I don't think it's a stretch to say Microsoft is costing its customers billions by now fixing this.
Pascal Kroeze - BICT GROEP B.V. commented
The 5000 limit per document libary is not working for most of our customers.
Seems we need to look for an alternative, impossible to cut this in pieces of 5000 for most of our big customers.
Jan Kratky commented
This limit is very problematic for lists, mainly with lookups, connected Power Apps, etc... Please do something about it!
I've been advised we can't sync Sharepoint 365 Document libraries that have more than 5,000 items using the OneDrive client - this is essential for us to use! If this is correct we'll have to migrate to Google
Please do not waste your time with sql server anymore, rework your backend!
Use a nosql database for metadata and skip the dusty database design.
The continual claim of supporting libraries of up to 30,000,000 items and then telling us "but we can only show 5,000 at a time" is quite simply ludicrous. Just today I've been told that the issue I have scrolling a large folder when it keeps refreshing and taking me back to a point higher up the list of content so making it impossible to scroll the entire folder (of less than 5,000 items) is actually caused because the library itself has more than 5,000 items in it. Things have got better of late with better indexing and the modern views but 5,000 is still simply too low of a limit to be useful and it certainly sometimes appears that Microsoft (perhaps support) are simply hiding behind that number and using as the excuse for everything that doesn't work as it should
Everyone should tweet @jeffteper about this. He is Corporate Vice President - Microsoft 365 with Teams, SharePoint, OneDrive, Viva, more.
kevin moore commented
a limit of 5000 is a joke when working with media files for a documentary this is never mention upfront when ordering the one drive for business - not good