Hi everyone,

I’m encountering a frustrating issue with dynamically filtering data on Web Part Pages in SharePoint using the Query String (URL) Filter Web Part, and I’d love some guidance.

Setup:

I have a document library with over 15,000 items (and growing). Two relevant columns are School and Archived—both of which are indexed.No single school will ever have more than 5,000 documents, so I assumed I could bypass the 5,000-item threshold when filtering the document library on the web part page.

My Configuration:

I’m using a Query String (URL) Filter Web Part to dynamically filter multiple Document Library Web Parts based on the “School” parameter passed via the URL (e.g., ?School=XYZ).This works perfectly without any filters applied to the document library web part views.

The Problem:

As soon as I add a filter in the document library view (e.g., Archived = Yes), I hit the infamous “cannot exceed 5000 items” error.This makes me believe that the archived filter in the document library web part triggers before the URL query string filter, causing the list view threshold error.

My Goal:

I need to figure out how to make the Query String (School) filter apply first, before any additional view filters like “Archived = Yes” get applied.

Previous Working Setup (SharePoint Designer):

When SharePoint Designer (SPD) was available, I could set up parameters using “Get Parameters From” rather than filters, allowing me to prevent the 5,000-item error by filtering inside the document library web part.I’ve used this setup on other pages successfully in the same environment, but I no longer have access to SPD.Now, I get the error: “The consumer Web Part did not provide schema information.”

Ideas and Solutions I’ve Tried (and where I’m stuck):

Parameter-Based Filtering: I want to be able to add a parameter like School = {Param1} inside the document library view filter. This used to work when I could use SPD. Does anyone know of a way to enable parameter-based filtering now that SPD isn’t available?Script Editor/Web Part Sequence: I think the problem might be that the Archive column (with over 5,000 items) loads before the School filter gets applied. Is there a way to force the School filter to load first, possibly using a Script Editor Web Part to control the filter sequence?

Constraints:

I cannot install any custom solutions like SPFx, and I have to use Web Part Pages because the modern experience doesn’t support the Query String URL Web Part in the same way.

Thanks in advance!

​Hi everyone,I’m encountering a frustrating issue with dynamically filtering data on Web Part Pages in SharePoint using the Query String (URL) Filter Web Part, and I’d love some guidance. Setup:I have a document library with over 15,000 items (and growing). Two relevant columns are School and Archived—both of which are indexed.No single school will ever have more than 5,000 documents, so I assumed I could bypass the 5,000-item threshold when filtering the document library on the web part page.My Configuration:I’m using a Query String (URL) Filter Web Part to dynamically filter multiple Document Library Web Parts based on the “School” parameter passed via the URL (e.g., ?School=XYZ).This works perfectly without any filters applied to the document library web part views. The Problem:As soon as I add a filter in the document library view (e.g., Archived = Yes), I hit the infamous “cannot exceed 5000 items” error.This makes me believe that the archived filter in the document library web part triggers before the URL query string filter, causing the list view threshold error. My Goal:I need to figure out how to make the Query String (School) filter apply first, before any additional view filters like “Archived = Yes” get applied. Previous Working Setup (SharePoint Designer):When SharePoint Designer (SPD) was available, I could set up parameters using “Get Parameters From” rather than filters, allowing me to prevent the 5,000-item error by filtering inside the document library web part.I’ve used this setup on other pages successfully in the same environment, but I no longer have access to SPD.Now, I get the error: “The consumer Web Part did not provide schema information.” Ideas and Solutions I’ve Tried (and where I’m stuck):Parameter-Based Filtering: I want to be able to add a parameter like School = {Param1} inside the document library view filter. This used to work when I could use SPD. Does anyone know of a way to enable parameter-based filtering now that SPD isn’t available?Script Editor/Web Part Sequence: I think the problem might be that the Archive column (with over 5,000 items) loads before the School filter gets applied. Is there a way to force the School filter to load first, possibly using a Script Editor Web Part to control the filter sequence? Constraints:I cannot install any custom solutions like SPFx, and I have to use Web Part Pages because the modern experience doesn’t support the Query String URL Web Part in the same way. Thanks in advance!  Read More

​