OData filter combining multiple or statements with and

[WillPage]

Hello,

I need to filter a SharePoint Get files (properties only) action to return items that match either one of several content types with a Created gt 'addDays(utcNow(),-7)' filter to get a list of documents that have been created in the past week and match one of a few content types.

My filter goes something like...

Created gt 'addDays(utcNow(),-7)' and ContentType eq 'Invoice' or ContentType eq 'Remittance'

What I get is every remittance on the whole document library created any time and every invoice created in the past 7 days.

How can I bracket these statements? I can move the Created gt filter out to a condition but then when I perform an action on the result (build an html table) I get an automatic for each. The whole filter needs to be in the initial get files action so I can build a single html table that matches my filter.

Is this possible? If not, is there a workaround?

[v-yamao-msft]

Hi @WillPage,

Instead of using a Condition, please try to use the action Filter array. Then in the action Create HTML table, it would be able to select value from the filtered items.

Please check the following image for a reference:

 

Best regards,

Mabel

[WillPage · Accepted solution]

Hi Mabel,

I got around this by bracketing the statements:

Created gt 'addDays(utcNow(), -7)' and (ContentType eq 'Invoice' or ContentType eq 'Remittance')

I don't know why I didn't try that before posting here, but thanks anyway; I have another use for the Filter array action so I still learned something from you!

[v-yamao-msft]

Hi @WillPage,

Thanks for sharing and updating.

I am very glad that you have figured it out and it is working for you now.

Best regards,

Mabel

[rschneider]

Hi @v-yamao-msft ,

Why should I use a filter instead of the query? My thoughts behind using the filter: Make SharePoint connector do heavy lifting of sifting through thousands of items and have flow work with much smaller subset later. Hoping this improves performance. Is this the case? Or would it actually be much faster the other way around?

Assumptions: ca. 100000 items in SP List, need to select only max. 10.