List View Threshold Blocks a Filtered View: Causes and Workarounds

When you open a SharePoint list view that should display only a few items but instead shows an error message or an empty result, the list view threshold is likely blocking the view. This happens because SharePoint enforces a 5,000-item limit per view for lists and libraries in SharePoint Server and SharePoint Online. The threshold prevents queries from scanning more than 5,000 items at once, even if the view is filtered to return fewer items. This article explains why the threshold blocks filtered views and provides practical workarounds to restore access to your data.

Why the List View Threshold Blocks a Filtered View

The list view threshold is a SharePoint performance safeguard. It prevents queries that would scan more than 5,000 items in a single operation. When a view applies a filter, SharePoint must evaluate each item in the list to determine whether it matches the filter condition. If the list contains more than 5,000 items total, the query fails because the scan would exceed the threshold, even if the filtered result set is small.

The key technical detail is that SharePoint uses the indexed column in the filter to limit the scan. If the filter column is not indexed, SharePoint scans every item sequentially. When the list grows past 5,000 items, that full scan is blocked. This is why a filtered view that worked when the list was small breaks once the list exceeds 5,000 items. The error message you see depends on the client: in the browser you may see “The attempted operation is prohibited because it exceeds the list view threshold,” while in SharePoint Designer you might get a generic query failure.

Another common scenario is when the view uses a filter on a column that has an index but the filter is not a supported operator. For example, filters using “contains” or “begins with” on a text column require a full scan even if the column is indexed. In that case, the threshold still blocks the view. Understanding these two root causes — lack of an index and unsupported filter operators — is critical to selecting the correct workaround.

Workarounds to Fix a Filtered View Blocked by the Threshold

Use the following methods in order of preference. Start with the simplest workaround, which is adding an index to the filtered column. If that does not work, move to the next method.

1. Add an index to the filtered column
   Go to List Settings > Indexed Columns > Create a New Index. Select the column used in the view filter and click Create. If the filter uses multiple columns, create an index on each column used in the filter. After the index is created, the query scans only the items that match the filter, bypassing the 5,000-item scan limit.
2. Change the filter to use an indexed column
   If the current filter column cannot be indexed (for example, a calculated column or a column with unsupported data type), modify the view to filter on a different column that can be indexed. For instance, if the view filters on “Title contains X,” change the filter to “ID greater than 0” and then add a second filter on the indexed column. This forces SharePoint to use the index.
3. Increase the list view threshold in SharePoint admin center
   In SharePoint Online, go to the SharePoint admin center > Content Services > List View Threshold. You can increase the threshold up to 50,000 for object model queries. This change applies to all sites in the tenant. In SharePoint Server on-premises, increase the threshold in Central Administration > Web Application Management > General Settings. Raising the threshold is a temporary workaround because the list may continue to grow.
4. Create a new view with a date range filter
   If the list has a date column (like Created or Modified), create a view that filters by a date range. Add an index on the date column. For example, filter “Created is greater than [Today]-30” to limit the items to the last 30 days. SharePoint uses the date index to scan only the matching items.
5. Break the list into multiple smaller lists
   If the list regularly exceeds 5,000 items and you cannot avoid full scans, split the data into separate lists by year, department, or category. Create a custom view or a lookup column to connect the lists. This is the most permanent workaround but requires data restructuring.

If the Filtered View Still Fails After Adding an Index

Adding an index does not guarantee the view will work if the filter uses an unsupported operator. The following issues are common.

Filter uses “contains” or “begins with” on a text column

These operators require a full scan even on an indexed column. Change the filter to “equals” or “is exactly” if possible. If you need partial matching, use a lookup column with a managed metadata term set instead.

Filter uses multiple columns but only one is indexed

SharePoint can use only one index per query. If the view has filters on two columns, index the column with the highest selectivity (the column that reduces the result set the most). Alternatively, combine the two columns into a single calculated column and index that calculated column.

Filter value is a user- or group-type column

User and group columns can be indexed, but the filter must use the “equals” operator. If you use “is equal to [Me],” SharePoint resolves the current user at query time. This works with an index on the user column. If the filter uses “contains” for a group, it will fail. Switch to a People Picker column with a single-user selection and index that column.

View still shows empty result or error in SharePoint Designer

SharePoint Designer uses a different query engine that is more sensitive to the threshold. If the view works in the browser but not in SharePoint Designer, create a new view in the browser and use it in the workflow or data source. Do not modify the view in SharePoint Designer.

Indexed Filter vs. Increased Threshold: Key Differences

Item	Indexed Filter	Increased Threshold
Implementation	Add index on filtered column in list settings	Change threshold in admin center or Central Administration
Effect on performance	Queries scan only matching items, improving speed	Queries scan up to 20,000 or 50,000 items, slowing performance
Permanence	Permanent as long as the index exists	Temporary; the list may outgrow the higher threshold
Supported filter operators	Only “equals,” “not equals,” “greater than,” “less than”	All filter operators, but only within the threshold limit
Administrative scope	Per list or library	Per web application (on-premises) or tenant (online)

You now understand why the list view threshold blocks filtered views and how to work around it. Start by adding an index to the filtered column and changing the filter operator to “equals” if needed. If the list continues to grow beyond 5,000 items, consider splitting the data into multiple lists. For advanced cases, increase the threshold temporarily in the SharePoint admin center. The most reliable long-term solution is to design views that always use indexed columns with supported operators.