In this case we want to filter on Contoso. Lastly, we need to provide a value that we want to filter on. Don't use the = symbol otherwise you will get a runtime error. In this case we want to use = which is represented as eq in OData. The breakdown of this syntax is we need to provide the name of the field in the source system (i.e. Inside this textbox we will provide a statement of CustomerName eq 'Contoso'.

After providing a Table name we also have the ability to provide a Filter Query.

Inside of Microsoft Flow, we can add a SQL Server – Get Rows action.

From Microsoft Flow, we want to return only rows where the Customer Name is equal to 'Contoso' We have the following Azure SQL database with a table that contains many work orders. Scenario #1: Get Rows from SQL Server and filter on Customer Name

In this blog post we are going to explore some popular OData filter expressions that you can use with some of our most popular connectors including SQL Server, Dynamics 365 and SharePoint Online. Some of the benefits of using OData include reducing the amount of data you are bringing into your flow, thus reducing the need to loop through a record set to find values of interest. Since Microsoft Flow's connectors are built-upon RESTful APIs, many of our connectors support the ability to filter datasets server-side using OData. One of the capabilities of OData is providing the ability to filter data using a standardized method across RESTful APIs, regardless if they are vendor provided or custom developed. OData (Open Data Protocol) is an OASIS standard that establishes best practices for designing RESTful APIs.

Online app builder odata feed