SharePoint Document Issues

Fix Power Automate Filter Query Not Finding SharePoint Document Set

Natalie TaylorNatalie Taylor Oct 29, 2026 868 views

Question details

Users are unable to retrieve a SharePoint Document Set using the Power Automate 'Get Files (properties only)' action with a filter query, despite having the correct values.

How to Fix Power Automate Filter Query Not Finding a SharePoint Document Set
Product
Power Automate
Device & OS
not provided
Scenario
Using the 'Get Files (properties only)' action in Power Automate to filter and find a specific SharePoint Document Set.
Observed behavior
The action returns empty results or fails to find the Document Set even when the column contains the expected value and uses the correct internal name.
Before you start

Ensure you have the correct permissions to access the SharePoint site and that the Document Set feature is properly activated in your SharePoint Site Collection features.

Solution 1Recommended

Verify OData Filter Syntax and Internal Column Names

Check the exact internal name of the SharePoint column and ensure the OData filter syntax is correctly formatted for the data type.

Power Automate relies on strict OData syntax to filter SharePoint records. A common cause for empty results is using the display name of a column instead of its internal name, or missing the required single quotes around text values.

1
Find the internal column name

Go to your SharePoint list settings, click on the column you are trying to filter by, and look at the URL in your browser. The internal name is the text after 'Field=' at the very end of the URL.

2
Check data types and syntax

Ensure the data type of the column matches your query formatting. Text fields require single quotes around the value (e.g., Title eq 'YourValue'), while number fields do not (e.g., ID eq 123).

3
Verify content type filtering

If you are specifically looking for Document Sets, add a filter for the Content Type. You can use the syntax ContentTypeId eq '0x0120D520...' to ensure only Document Sets are returned.

Verify OData Filter Syntax and Internal Column Names
Internal Name Changes: If a column was renamed after creation, its internal name remains the original name it was created with. Always verify via the URL method.
Free Microsoft Office alternative

Manage Your Documents Efficiently with WPS Office

While troubleshooting complex SharePoint and Power Automate workflows, you need a reliable and lightweight office suite to handle your daily document tasks. WPS Office is a powerful, free alternative to Microsoft Office that offers seamless compatibility with Word, Excel, and PowerPoint files.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the software: Run the downloaded setup file and follow the on-screen instructions to install WPS Office on your device.
  3. 3. Open and edit files: Launch WPS Office and instantly open your existing Microsoft Office documents with perfect formatting.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight and fast, ensuring smooth document editing without heavy system requirements.Familiar user interface makes migration effortless with zero learning curve.Built-in PDF editing and conversion tools for comprehensive document management.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Power Automate require internal column names for SharePoint filter queries?

Power Automate uses the OData protocol to query SharePoint data. OData requires the original internal name of the column, which does not change even if you rename the column's display name later in SharePoint settings.

How do I filter by Content Type to only get Document Sets?

In the Filter Query field of the 'Get files (properties only)' action, you can use the syntax ContentType eq 'Document Set' or filter by the specific Content Type ID if you have created a custom Document Set type.

Can I use 'Get items' instead of 'Get files' for Document Sets?

Document Sets are technically folders with metadata stored in a Document Library. Therefore, you must use the 'Get files (properties only)' action rather than 'Get items', which is meant for SharePoint Lists.

Why do text filters need single quotes in Power Automate OData queries?

In OData syntax, single quotes are used to denote string values. Without them, Power Automate attempts to read the text as a column name or a function, which results in an invalid query error.