I have a requirement on Microsoft Flow. Depending upon my requirement, I have a SharePoint List and in that list, I have one Yes/No field column.
When I am trying to put this Yes/No field Column in flow Condition is equal to true/false or 0/1, Always the condition returns as "no" even if it is true. How can I resolve this issue?
Below is the flow screenshot:
I don't know if it's related, but I have a flow I'm working on, and last week, my conditions where working perfectly, but now they seem to return false (no) and I can't figure out why. At this moment I'm still trying to figure out what's wrong.
This should return true, if the three fields are cleared, but it always returns false, even if they are cleared.
I can get it to return true (yes), if I change "is equal to" to "is not equal to".
As I said, this was working last week.
Hi @Preetish ,
Could you provide more details about the field you mentioned?
Do you have any special treatment for it?
Basically the return value of Yes/No field is true and false.
I did a test on my side. If Yes is selected in the field, the result of Condition judgment will be true.
You could try adding a Compose action on Condition to output the return value of the current field to see if this field selects Yes or No.
Please take a try and see if issue still exists.
If the problem persists, please provide Flow run history, including the results of Compose output so that we can analyze the problem.
I have the same issue. I tried adding compose to the condition, which returns the Yes/True as it should, but it still prompts false.
The op's screenshot shows the word "true" being manually added which won't work. Has to be an expression you can look up. Not very intuitive and poorly documented as usual.
One thing to add is that (for me at least) when you type true in the expression input box and click the autocompleted 'true' (in blue text with the little icon next to it on the left as shown in the image above), then click OK, you might get an error saying "The expression is invalid". IGNORE THAT! It's an annoying little bug. Simply click OK to close the error dialog box and then click OK underneath the expression input box and, this time, the "error" will not appear and true will appear in the condition box in a pink box with the 'fx' icon next to it on the left (as shown in the image above)
Thought I would add that if you are using "experimental features" I am showing a bug where the true/false/null functions show up as undefined.
Experimental Features enabled:
Experimental Features disabled:
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
At the monthly call, connect with other leaders and find out how community makes your experience even better.
If you are a small business ISV/Reseller, share your thoughts with our research team.