1. Odata Query Syntax Filter

MSFlow filter SharePoint list in GetItems action by date field I was attempting to create a flow that executed a GetItems action that would use the ODATA filter field to limit the rows to those where a date field (ProjectEnd) was less than or equal to the current date/time.

Odata Query Syntax Filter

Hi,Would it be available to filter the SharePoint lists with Condition under Microsoft Flow?Currently OData filters are not implemented yet by all connectors.See the response from in the following thread:But the filter query works for SharePoint lists.Currentlly the Filter Query under the Action Act as thein OData Query,The Order By act as the:There is no query implemented under the Action.So if you would like to return special fields from the SharePoint list (See, you may consider submit this as an idea, to add the $Select as an available Query under the Get Items Action.Regards,Michael. Curious if you have gotten this to work. I have tried every permutation imaginable and have not been able to get this to workField Name eq 2 Part ValueField Name eq 2%20Part%20ValueField Name eq '2%20Part%20Value'Field Name eq '2%20Part%20Value'Field Name eq '2 Part Value'Field Name eq '2 Part Value'Fieldx0020Name eq 2 Part ValueField x0020Name eq '2 Part Value'Fieldx0020Name eq '2 Part Value'Fieldx0020Name eq 2%20Part%20ValueFieldx0020Name eq '2%20Part%20Value'Fieldx0020Name eq '2%20Part%20Value'Every single one has been tried, none of them work, so do Odata filters really work? Hi,Yes, it works.Please add a condition, put the corresponding field dynamic content into the first Input Box, then click advanced mode, then you should be able to find the proper field identifier:The field name here is Testing Text, while the workable column field is marked as 'haiz'So if we would like to take use of this column to filter query, the formula should be:haiz eq 'TextValue'For the value part, it is the actual text, no need to replace the Space with other charactor.Regards,Michael.

For those that have trouble with List.Contains, you might need Table.Contains instead.Had the same requirement for a project using Power Query for Excel. The table containing the values to be passed to the filter was in a table on an Excel sheet, so end users could update the values as needed. I created a query to reference that table, 'tblAgents' with a header value of 'AgentID.'

To help understand the syntax, let's assume the table that I want to filter has a column of 'AgentIdentifier.' Here's the code that works for me:#'Filtered Rows' = Table.SelectRows(Source, each Table.Contains(tblAgents, AgentID = AgentIdentifier)). Hello,The initial solution does work. Here are some details to make it work.In Power Query, you must load a table containing your facts (lots of rows) and an other table containing the filter criterias (a few rows). Your Filter table must be converted to a List. The filter table will contain only one column, right-click on the column header and select Drill Down: the filter table is now a List.List.Contains already includes the notion of 'any'.