This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 53%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
SharePoint 2013 Foundation On-Prem
This error is from Excel that is linked to a Tasks list which is now exceeded the LVT, which I previously increased to 10,000. I have the same issue with most of my views on the tasks list itself and even after reading a lot of articles regarding indexing, filtering results and this still doesn't make sense to me.
Moving to the server first and a standard view that is created with the following filters.
The list currently has 10447 items;
ViewName: Task Cleanup
So with the view using a indexed column as the 1st filter and the filtered result is under the LVT, I am not sure why this view is having the error?
"This view cannot be displayed because it exceeds the list view threshold (10000 items) enforced by the administrator."
What am I missing?
When using the server/administrator to look at this view, there were "0" results. I reduced the [modified] filter to 30 days (instead of 60) and there are now 5065 results.
Again this is clearly under the LVT of 10,000 so still not sure why this is not working.
I then removed the "Modified <= [Today]-60" filter leaving only the "Status (indexed) = Completed" in case the 2nd filter was causing the issue and still getting the LVT error.
Hi @S A ，
We are currently researching this issue, any update will be post here.
Thanks for your support and understanding. :)
Regards,
Elsie Lu
Is there anyone that can either explain this or provide direction to an article that does, thanks?
since you are working on-prem you may try the following: run SQL server profiler and check what exact SQL query is executed when you open your view and how many records it returns from the table. It looks like that it still gets all records (which causes throttling) and only after that filters them. In general what you did (limiting number of items by adding extra filters) should help with such problems.