Flow with Trigger Conditions of Yes/No

[cadutcher]

I am trying to start a flow with a create or modify an existing item action with trigger condition on a single select field of yes no. The logic I have used for other flows is not working- @equals(triggerBody()?['Submit for Review']?['value'],'Yes') - any ideas?

[RobElliott]

@cadutcher try using true instead of Yes.

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.

[cadutcher]

so this instead: @equals(triggerBody()?['Submit for Review']?['value'],true)

[JohnAageAnderse]

Hello @cadutcher 

@RobElliott  is right, you should use the value true, as you asked in the last post.

There is an additional issue with your expression - you have to use the columns internal name! That is the name without spaces!

Look at the list settings and check what is the real column name. If you did like me, then it would be "SubmitForReview" but if you defined it with spaces in the name, then the internal name would be "Submit_x0020_for_x0020_Review".

Also, remove the "?['value']" part, a Yes/No column does not have that!

Try it out and have fun 🙂

Kind regards, John

[v-alzhan-msft]

Hi @cadutcher ,

Have your problem been solved by @JohnAageAnderse  and @RobElliott 's solution?

Please take a try and let me know if the issue could be solved, if not, please share the run history of the flow when it has run failed and I would provide a proper solution for you.

Best Regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[cadutcher]

Hi Alice, 

Thanks for connecting. 

The flow is succeeding, but the trigger logic is not holding. The action triggers on both yes/no rather than stopping at false. Any ideas?

[v-alzhan-msft · Accepted solution]

Hi @cadutcher ,

Could you please share the screenshot of the configuration of the flow?

I have made a test on my side and I find the trigger condition wouldn't work now since the output of the item from the when an item is created or modified is an array now.

You could only add the condition under the trigger to achieve the requirement, and you could leave the if no branch blank if the condition don't meet.

What is the type of the single select field that you mentioned? Is it a Choice type field? Or is it a Yes/No type field?

If it is a Yes/No type field, you could refer to screenshot below to create the flow:

Best Regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[CWalker0033]

Hi, I have tried several variations of trigger conditions to initiate a workflow when "Yes" is selected in a "YES/NO" column on my sharepoint when it is modified,  but I have not been successful. Any ideas/suggestions would be greatly appreciated. 

[stingray]

This seems to be hit of miss whether this works or not, i have a 2 separate lists and flows using the the same code.

@equals(triggerBody()?['_triggerApprovalFlow'],true)

Both have the same column names for the trigger control column, one triggers when modified, the other doesn't. The one that doesn't work does have somewhat more columns than the one that's does work, it also might be to many look ups in the list as well as that seems to break PowerApps so its a good chance it breaks Flow.

[stingray]

Ok for anyone else having issues on this and it not making sense why it's still not working, i checked the raw outputs of my trigger and in my case my column "_triggerApprovalFlow" is coming back as "OData__triggerApprovalFlow"

When changing to @equals(triggerBody()?['OData__triggerApprovalFlow'],true) the Flow now only triggers when that column is yes.

This could be because my column naming convention uses underscore, but id have to test. 

[PrimalEdge]

Not sure if this is still an issue for folks, but after a ton of searching I discovered that when using a Yes/No field you need to

1. Use True or False for Yes and No respectively.
2. You cannot use the 'True' format, but rather just True without the single quotes.

So, your Trigger Condition might look something like this:

@equals(triggerBody()?['YourFieldNameHere'], True)

One last tip, split array at the top of the settings panel (for me anyway) is hit or miss as to whether or not it is active.  Be sure it is on and that your Array is set to: @triggerOutputs()?['body/value'] in the drop down.  Hope this helps!