Inconsistency in Power Automate Desktop's "If" Condition Configuration

(0) Share

Report

Posted on by CU12071944-0

Issue Summary
While working with Power Automate Desktop (PAD), I encountered a significant inconsistency between the official documentation and the actual behavior of the "If" condition action in the latest version of the tool.

According to the documentation, the "If" condition is expected to have three arguments:

Operator (e.g., =, ≠, >, <)
First operand
Second operand
However, in the current version of PAD, the "If" condition only provides a single input field labeled “Conditional expression”, which expects a complete boolean expression. This change is not reflected in the documentation, leading to confusion and failed attempts to implement basic logic.

Examples of the Problem
We attempted several common logical expressions that should evaluate to true, but they failed to compile:

❌ Attempted: (2 == 2)

Result: Compilation error – expression not recognized as boolean.

❌ Attempted: 2 == 2

Result: Compilation error – == is not a recognized operator.

❌ Attempted: 2 = 2

Result: Compilation error – not interpreted as a valid boolean expression.

❌ Attempted: =(2==2)

Result: Compilation error – expression not recognized as boolean.

❌ Attempted: =(2=2)

Result: Compilation error – expression not recognized as boolean.

❌ Attempted: (%2% == %2%)

Result: Compilation error – expression not recognized as boolean.

✅ Only this worked: =true and =false

Result: Compiles and runs correctly, but does not allow for dynamic comparisons.

Impact
This inconsistency:

Prevents users from writing even the simplest conditional logic without trial and error.
Breaks compatibility with examples and tutorials based on older versions.
Makes it unclear which syntax is supported in the new “Conditional expression” field.
Increases the learning curve for new users and frustrates experienced ones.

Recommendation
Update the documentation to reflect the new single-field syntax and provide clear examples of valid expressions.
Clarify supported operators (=, <>, >, <, etc.) and whether parentheses or functions like not() or and() are supported.
Optionally, restore the three-field format or provide a toggle between "basic" and "advanced" modes for conditions.
Would you like this formatted as a PDF or Word document for submission or sharing? I can generate that for you too.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

eetuRobo 4,539 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

You are correct that (at least as of now) the documentation does not always match how the Power Automate Desktop power fx works. Power Automate Desktops Power Fx is fairly new and is bit different than what is used in Power Apps which the documentation usually refers to. Power Fx in PAD doesn't seem to have "Equals" -fucntion

The regular flows (non power fx enabled) are more straight forward and easier and match the documentation better.

This works with Power Fx in PAD:

Works with different values:

Was this reply helpful? Yes No
Suggested answer

Riyaz_riz11 4,150 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

Working Syntax Examples:

1. Basic Comparisons:

%Variable1% = %Variable2% %Number1% > %Number2% %String1% <> %String2% %Value% >= 10 %Count% <= 100

2. Multiple Conditions with Logical Operators:

%Variable1% = %Variable2% AND %Number1% > 5 %Status% = "Active" OR %Status% = "Pending" %Count% > 0 AND %Count% < 100 NOT %IsEmpty%

3. Function-Based Conditions:

%Text.Contains(InputText, "keyword")% %DateTime.Now% > %TargetDate% %List.Count% > 0

4. Complex Expressions:

(%Variable1% = "A" OR %Variable1% = "B") AND %Number% > 10 %Text.Length(InputString)% > 5 %Math.Mod(Number, 2)% = 0

Key Rules for Success:

1. Variable References:

Always wrap variables in %VariableName%

Don't use parentheses around individual variables like (%Variable%)

2. Operators:

Use = for equality (not ==)

Use <> for not equal (not !=)

Use >, <, >=, <= for comparisons

Use AND, OR, NOT for logical operations

3. String Comparisons:

%TextVariable% = "Expected Value" %Status% <> "Error"

4. Numeric Comparisons:

%NumberVariable% > 10 %Counter% = 0 %Result% >= %MinValue%

Complete Working Examples:

Example 1: Simple Comparison

Action: If Condition: %UserInput% = "Yes"

Example 2: Multiple Conditions

Action: If Condition: %Age% >= 18 AND %Status% = "Active"

Example 3: Function-Based

Action: If Condition: %Text.Contains(EmailAddress, "@")%

Example 4: Complex Logic

Action: If Condition: (%Type% = "A" OR %Type% = "B") AND %Count% > 0

Why Your Attempts Failed:

❌ (2 == 2) - Wrong operator (== instead of =) and unnecessary parentheses
❌ 2 == 2 - Wrong operator
❌ =(2=2) - Don't start with = and don't use parentheses around simple comparisons
❌ %2% == %2% - Wrong operator

Correct Versions:

✅ 2 = 2
✅ %Variable1% = %Variable2%
✅ %Number% > 5

Testing Your Conditions:

Set up test variables:

SET Variable1 TO 2 SET Variable2 TO 2

Use simple condition:

IF %Variable1% = %Variable2%

For debugging, use Display message:

Display message %Variable1% & " equals " & %Variable2%

If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍. Regards, Riyaz

Was this reply helpful? Yes No