You’re offline. This is a read only version of the page.
Hi everyone,
Hope you are having a good day!
I am creating a flow that will get items from a sharepoint list with this filter on the query:
I've tried both,
ApprovalID eq <integervariable> and Cancelled eq 'true'
@yashag2255 hope you can help.
@RobElliott
and
ApprovalID eq <integervariable> and Cancelled eq true
but neither seems to work since the query gets the item with the correct integer value but does not take into consideration the second query filter I've used, the 'Cancelled' column is a Yes/No Column in Sharepoint.
I'm patching the column "Approved" in Powerapps and after the patch, the do until of my flow stops even though there is no "Cancelled" eq true.
I don't know how this bug still presets, but thank YOU
This magically works! Thanks for the answer!
4 years later, i can't believe i will get the same issue and spent hours and hours talking to ChatGPT and asking for help. i tried different combinations:
fld eq Yes , fld eq 'Yes'
fld eq true, fld eq 'true'
'fld eq yes' and so on...
did fld ne false and it worked but that's weird though. so, asked copilot and told me to try fld eq 1 and it worked! 🙂
It's not a secret name, it's the internal name of the column and it doesn't change. When making changes to column names you always need to check the internal name when referencing the column n JSON, Power Apps or Power Automate., This is particularly so if your column name has spaces or special characters in it as SharePoint might add something like, for example, _x0020_ which is the url encoding for a space. Or it might strip out the space altogether. So the internal name is very important.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.
FYI - for those troubleshooting this I ran into another PA shortcoming that compounds this one. I found that I was using the list in MS teams and making adjustments there, but when looking at the full JSON that returns when getting the filtered list my problem was this: There's a column name I see and can change in teams, but then there's the secret name that actually matters which is likely seen in sharepoint (I can't verify that now as i've lost access temporarily). It decided the names like this:
seen in teams / power automate = seen in JSON data / probably sharepoint
responder = responder
responder2 = responder20
responder3 = responder2
So the value for the column in the ODATA filter needs to match what is in the JSON data, not what is in teams. this caused me a good deal of lost time troubleshooting changes to the responder2 column as me and the code disagreed which column we were talking about.
Filtering in PA with Yes/No Sharepoint Column is a 0 or 1 so "Yes/no Column eq 0 " would return false values and an eq 1 would return true values
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (
