列表视图限制
我有两个环境:SharePoint 2013(带有CU 2017年8月)和SharePoint 2016(带有CU 2017年8月)
I have two environments: SharePoint 2013 (with CU 2017 August) and SharePoint 2016 (with CU 2017 August)
文档库的根目录中有5500个文件夹.
Document library with 5500 folders in the root.
列表视图显示所有内容而不进行过滤，但应用了分页(每页30个项目)
List view that shows all the contents without filtering but paging is applied (30 items per page)
当我尝试使用非管理员用户帐户访问此视图时，得到的结果取决于SP 2013或SP 2016.
When I try to reach this view with non-admin user account, I get different results depends on SP 2013 or SP 2016.
在SP 2013中，我得到了:
In SP 2013 I get this:
此视图无法显示，因为它超过了由行政人员.
This view cannot be displayed because it exceeds the list view threshold (5000 items) enforced by the administrator.
要查看项目，请尝试选择其他视图或创建新视图.如果您没有足够的权限来为此列表创建视图，请要求管理员修改该视图 使其符合列表视图阈值.
To view items, try selecting another view or creating a new view. If you do not have sufficient permissions to create views for this list, ask your administrator to modify the view so that it conforms to the list view threshold.
了解有关 为大型列表创建视图
Learn about creating views for large lists
您能否解释一下为什么用户看不到查询的30个项目(而不是5500). SharePoint 2013以不同的方式威胁极限是众所周知的事实吗?
Could you explain why user can't see 30 items that are queried (not 5500). And is it a known fact that SharePoint 2013 threats the limit differently?
我已阅读到SharePoint 2016自动添加索引列，但我无法理解应该使用哪些列进行索引以使此视图在SP 2013上正常工作.
I've read that SharePoint 2016 adds index columns automatically, but I can't get my head around what columns should be indexed to make this view working on SP 2013.
首先，让我们谈谈潜在的问题. 当用户尝试查看他们不查询30个项目的项目时，他们将检索所有5500个项目，然后将该结果集过滤到排序后的前30个项目中.为防止您 必须创建一个索引列，该索引列可用于减少检索到的记录数.如您所读，2016年会为此自动创建索引列. 2013年，您必须找出要手动建立索引的栏. 没有 了解有关您的库和列的更多信息后，很难预测该索引列将是什么.
First, lets talk about the underlying problem. When the user tries to view the items they aren't querying for 30 items, they are retrieving all 5,500 and then filtering that result set down to the first 30 after sorting. To prevent that you have to create an index column that can be used to decrease the number of records retrieved. As you've read 2016 creates index columns for this purpose automatically. In 2013 you have to figure out which columns to index manually. Without knowing more about your library and the columns involved its hard to predict what that index column would be.