Tool · Power Automate · SharePoint + Dataverse
OData Filter Builder
Build the Filter Query for SharePoint “Get items” or Dataverse “List rows” in Power Automate, with the right quotes, dates and column names for each.
Works with
Power Automate
Dataverse- SharePoint
Conditions
and
Filter query
Paste into Get items → Advanced parameters → Filter Query.
Status eq 'Open' and Created ge '@{addDays(utcNow(), -7)}'- Use internal column names, not display names. Find one in List settings → click the column → the end of the URL (Field=…).
- On lists over 5,000 items, the first column you filter on should be indexed (List settings → Indexed columns).
Display name → internal name
SharePoint encodes spaces and symbols when a column is created. This shows the name it most likely got. If the column was renamed later, its internal name is still the original one.
Due_x0020_DateQuestions
FAQ
Why filter in the action instead of with a Filter array step?
A filter query runs on the server, so only the matching items come back. That is faster, uses fewer API calls, and avoids the default limits on how many items Get items and List rows return.
Why does SharePoint say the column does not exist?
The filter needs the internal name, which can differ from the display name: spaces become _x0020_, and renamed columns keep their original internal name. Check it in List settings by clicking the column and reading Field= at the end of the URL.
How do I filter by a date relative to today?
Tick fx on a date condition and pick a shortcut such as "7 days ago". SharePoint needs the date in quotes; Dataverse needs it without. The builder adds the right form for you.
Can I filter on a person or lookup column?
Yes. In SharePoint, filter a person column by email (Approver/EMail eq ...) and a lookup by its ID (ProjectId eq 5). In Dataverse, filter a lookup by the related row’s GUID on the _name_value column.
Is anything sent to a server?
No. The filter is built in your browser.