How to Build OData Filter Expressions for Power Platform
Use the OData Filter Builder to construct filter queries for Dataverse, SharePoint, and other OData APIs in Power Automate and Power Apps.
Tool Used
OData Filter Builder
Open the OData Filter Builder
Open the OData Filter Builder tool. The builder provides a visual interface for creating $filter query parameters without needing to memorize OData syntax. You will add conditions one at a time and combine them with AND or OR operators.
Add your first condition
Click Add Condition. Enter the field name — in Dataverse, use the logical name of the column (e.g., statuscode, revenue, createdon). Select the comparison operator: eq (equal), ne (not equal), gt (greater than), ge (greater than or equal), lt (less than), le (less than or equal), startswith, endswith, or contains. Enter the value. For string values, enter the text without quotes — the builder adds them automatically. For option set fields, enter the integer value, not the display label.
Add more conditions and combine with AND/OR
Click Add Condition to add additional conditions. After each condition, use the operator dropdown between conditions to choose AND (both conditions must be true) or OR (either condition can be true). For more complex logic with nested groups, use Add Group to create a parenthesized sub-expression. For example: (status eq 1 or status eq 2) and revenue gt 1000000.
Preview and copy the filter expression
The generated filter expression updates in real time as you add and modify conditions. Review the generated OData filter string in the preview panel to confirm it matches your intent. Click Copy to copy the filter expression. The copied text is ready to paste into the Filter rows field in a Power Automate List rows action or Dataverse API $filter parameter.
Use the filter in Power Automate
In Power Automate, open a List rows action (Dataverse) or Get items action (SharePoint). Click Show advanced options. Paste the filter expression into the Filter rows field. Test the action by running the flow manually. If you get a 400 error, check that field names match the logical names exactly (case-sensitive in some endpoints) and that option set values are integers, not strings. Combine with the Select columns field ($select) to retrieve only the columns you need.
All done!
You are ready to use OData Filter Builder like a pro.