Trigger condition on yes/no field never triggers

[KarlInOz1]

I'm starting to tear my hair out over this, I've tried every iteration I can think of but am not getting anywhere.

I have a flow that triggers every single time an item is modified but I only need it to trigger if my item is a Trainee. So I want to use the trigger condition. But I can't get it to ever trigger with the trigger condition.

My evaluation field is a yes/no field. The trigger condition I am trying is

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

 And it never triggers. But if I remove that trigger condition and make a change to a record where IsTrainee is Yes and then look at the output of the trigger body it shows:

"IsTrainee": true,

I have tried

@equals(triggerBody()?['IsTrainee'], true) 
@equals(triggerBody()?['IsTrainee'], TRUE) 
@equals(triggerBody()?['IsTrainee'], True) 
@equals(triggerBody()?['IsTrainee'], 1) 

and none of them works. I created a test flow without the trigger condition, initialised a boolean variable with the value of IsTrainee and it initialises as True. I am totally baffled as to what is going on. 

This is my Get Items settings page

[v-liwei-msft]

Hi @KarlInOz1 

Please try:

@equals(triggerOutputs()?['body/IsTrainee'],true)

Best Regards,

Levi

[KarlInOz1]

Hi @v-liwei-msft  thanks for your suggestion. That still doesn't work. I also notice an error on the Split on the Settings page with that expression there.

[v-liwei-msft]

Hi @KarlInOz1 

Please try:

Best Regards,

Levi

[KarlInOz1]

Hi @v-liwei-msft Thank you again.

Well this is interesting. I was able to select Split On to on, click Done, Save the flow with no errors given. But when I go back in to Settings I have the error:

I have no option to edit the text, there is only a drop down to select. It shows the error at the top and still doesn't trigger.

[VictorIvanidze]

Remove the trigger condition and test with simple condition action.

[v-liwei-msft]

Hi @KarlInOz1 

I suggest you try to use condition instead of trigger condition:

Best Regards,

Levi

[KarlInOz1]

HI @v-liwei-msft and @VictorIvanidze  Yes, this is how I started the journey. The flow has a condition statement and it works perfectly well. But it is being triggered every few seconds as records are being updated in my list constantly. I decided to utilise the trigger condition to reduce the number of times the flow runs but it seems the yes/no field cannot be used as a trigger condition from what I am experiencing. There are a few posts on the internet describing exactly what I am trying to do but it doesn't seem to work in our tenant. I even created a brand new flow to test this out, in case my original flow was corrupted in some manner but I have not been able to get the trigger condition to work.

[wskinnermctc · Accepted solution]

I got it to work by wrapping a 1 with bool(). So it reads it as true.

@equals(triggerOutputs()?['body/IsTrainee'],bool(1))

Here is a screenshot below.

Use the bool(1) expression in Trigger Condition

[KarlInOz1]

@wskinnermctc  Thank you! Yes that is the answer. And the query actually works with either

@equals(triggerOutputs()?['body/IsTrainee'],bool(1))

as you suggest, or 

@equals(triggerBody()?['IsTrainee'],bool(1))

[AijalonMosk]

You are awesome, haven't found any other answer as such as this.

[beebul]

Thanks this really helped me!!! 👍