Flow Condition throws FALSE even though output should be TRUE

[sb16]

Hi All,

I wanted to get your insight in to this flow I have created, which is triggered by a form which captures cost from a radio button list.
Once triggered it sends a Approval request which when approved is placed in a condition :

if approved AND cost is equal to 20 OR 30 sends an email saying the cost is 20 or 30.

Issue is that even when I select 20 or 30 in the form it still produces a FALSE result which causes the condition to fail.

Thanks

[Gus81live]

Hi @sb16 

One question, does the first condition for 10 ever fail?

Also, could you try checking the boxes in your conditions and testing again?

[sb16]

Hi @Gus81live 

If I select 10 the first condition does fail.

Isn't the check boxes just for grouping purposes?

[sb16]

Hi @Gus81live 

to clarify if I select 10 in my form the first condition returns FALSE and thus sends the email saying cost is 10.
This condition works correctly I want it to do that. 

But the second condition is where I'm confused. Why is it that the condition throws FALSE. 

[sb16]

Adding the Flow Result image too.

[SelimK]

could you initialize a variable with the 'cost' that you get from your form? 
It would be great if we could check if we get a value there.

[sb16]

Hi @SelimK 

Yes I have initialized a variable.

In the form I select 20.

[SelimK]

I see, I would suggest to debug your condition where your have a AND OR and the approve check.

Can you try only with the approve check? and delete the checks for 20 and 30?
if that works continue with the checks on 20 and 30 values one by one.

Alternatively, you could do the checks separately, First check will only check on the approve false or true. 
In the second check you can check if the values are 20 or 30 or 40

Personally, I would look into the switch statement after the check on approve if it meets your requirement.
Switch Statement using Power Automate - Power Platform Community (microsoft.com)

[wskinnermctc]

Yes @SelimK I think the Switch never gets enough respect. It is a great tool to prevent nested conditions.

@sb16 I would recommend wrapping the variable in the integer int() function. I would even wrap the numbers in the condition in the int() function. That way you know for sure you are comparing numbers to numbers. 

The alternative would be wrapping both in the string() function.

This might not be your problem, but it is something I always do just to prevent any possible issues. (It is annoying that even if you have a number field in a MS Form, it will come into Power Automate as a string.)

See about Conversion Function Reference here for the int() and string() use.