I'm doing a getFiles action step with the properties only.... trying to do contains (which is apparently a substringof).
I have tried contains and substringof - neither works.
I also couldn't find a good reference to this in the Msft documentation that is actively updated.
I am currently using a startswith odata filter successfully and not sure why this is rejected.
Hi @sasrsc
I have not seen any Docs that describe which Odata filters work for what connector.
You could also try using the 'Filter array' action
do you know if there's a webpage that tells you what odata filters work with different connectors?
Hi @sasrsc
Not all the ODATA filter queries are qualified to run via Power Automate connectors.
Thanks
Hi @Jcook thanks for that tip. I had been using that site and couldn't figure out why my specific use case was failing.
So I got this to work...
substringof('@{triggerBody()['text']}', Title)
Notice that the "search for this text" is before the variable that I'm searching in. I think I found that on another site.
I tried this...
contains(Title,'@{triggerBody()['text']}')
and I get this error...
The function operator 'contains' is not supported or its usage is invalid.
clientRequestId: a5bc9929-de80-4e9e-a10a-e060a2727bbe
serviceRequestId: a5bc9929-de80-4e9e-a10a-e060a2727bbe
I tried flipping them...
contains('@{triggerBody()['text']}',Title)
and the same error.
The person on this page is mentioning List Records in all their examples and not specifically querying a sharepoint list/document library, so I'm wondering if there are differences where SP won't accept some of those example Odata filters.
Hello @sasrsc
This post is very helpful:
https://diyd365.com/2019/11/20/every-power-automate-ms-flow-filter-query-you-ever-wanted-to-know-as-a-functional-consultant/
contains does work. If you’re having issues with contains, please post the error you are getting, with your syntax
ankit_singhal
7
Super User 2025 Season 1
Michael E. Gernaey
4
Super User 2025 Season 1
David_MA
2
Super User 2025 Season 1