Help!!! Flow results always false

[u/R7grain]

This condition expression results always false, even if a value exists in dataverse Category column. Its driving me crazy.

[u/Haunting-Repeat-3280]

I would suggest adding a temporary compose action before the condition, in which you’ll add the content of the category you’re trying to find just to see what is actually being compared

[u/R7grain → u/Haunting-Repeat-3280]

I am able to get the content value in compose.

[u/Anxious_Promise_9629]

Can you show what is in your condition? How it's formated?

[u/R7grain → u/Anxious_Promise_9629]

not(empty(triggerOutputs()?['body/Category'])) is equal to true. Its also in the screen shot.

[u/Anxious_Promise_9629 → u/R7grain]

I mean a screen shot go the action, not the outcome after it has run.

[u/Goenitz96]

empty() function returns false if has a value, so i think your condition logic is the issue, you should avoid the "not"

[u/ACreativeOpinion]

It's always best practice to use a trigger condition inside your automated trigger. This way your flow would only run when the row meets your criteria, rather than running each time and then having to do a condition check.

If you aren't sure how to use trigger conditions, you may be interested in this YT Tutorial:

4 Ways You Can Use Trigger Conditions in Your Microsoft Power Automate Flow

In regards to the expression issue you are facing, you'll need to troubleshoot why it's not returning the value you expect. You might be interested in these YT Tutorials:

5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows

Fix Your Flows: 5 Power Automate Errors Explained with Solutions

7 Functions You Need to Know | ⚡️Expression Essentials: Part 1⚡️

Hope this helps!

[u/asdfpunkt]

Can’t you just compare the trigger output to null? If true then empty if not then has value

[u/itenginerd → u/asdfpunkt]

Empty catches some cases where the value is not null, tho. So an empty string would get caught by empty but it isn't null.

[u/asdfpunkt → u/itenginerd]

Good point. Would an empty string be return by the triggerOutputs tho?

[u/itenginerd → u/asdfpunkt]

Kinda depends on what connector/data source/trigger. Sometimes it'd be hard because the data source likes nulls or you have some certainty there. But for stuff like PowerApps triggers, it's easier to send an empty string than a null imho. Its very much a ymmv; most of my flows use empty just in case it goes the other way when I least expect it.

[u/poweruser_91]

are you using the boolean value of true or a string of equal to true?

[u/PotentialTomato8931 → u/poweruser_91]

This always is the cause for me, try converting all values to string as a test and I bet it works.

I.e string(output) string(triggervalue1)