ODATA Filter Query not valid when it should be

Question

Hi,&nbsp;I’m deeply confused with Power Automate Get Items ODATA Filter Queries. They are completely illogical. With one choice column called “Status”, it works absolutely fine. With another choice column called “Sway Status” on the same list, it errors every single valid Filter Query I give it.&gt; The syntax is correct, it is identical syntax to the one that works.&gt; It recognises the column exists, otherwise it prints a different error along the lines of “The column may have been removed” when it can’t find the column&gt; I have tried quote escaping. Doesn’t workThe experimental feature to simplify filter queries isn’t there anymore, so I’m stuck with these queries that seem to only work if you’re lucky and the winds blowing in the right direction. Please help.

kelly_edinger · Answer

Have you tried using SwayStatus? When you go into List Settings and then click the column, the URL will show you the true column name at the end of the URL. It won't have any spaces.

benmercer · Answer

Just tried it. Still doesn’t work even without the spaces unfortunately.

damien_rosario · Answer

Hi&nbsp;BenMercer&nbsp;&nbsp;If SwayStatus eq 'To Do' didn't work, you can also try Sway_x0020_Status eq 'To Do'.&nbsp;Cheers and best wishesDamien

rahul-barua · Answer

To check the column name you could use the below URL to find the internal name of the column_api/web/lists/getbytitle('List Name')/fields

benmercer · Answer

Damien_Rosario&nbsp;this didn’t work either. Same bad request error. Like I said, it clearly knows the column exists, otherwise it throws back a different error when it can’t find the column. The bad request error seems to be it saying it’s found the column, but is complaining that the syntax is wrong, when it isn’t.

Forum Discussion

ODATA Filter Query not valid when it should be

Share

Resources