Help with trigger conditions using OR

(0) Share

Report

Posted on by smorley

546

Hi everyone, Happy Friday!

I've been reading this post on Trigger Conditions:

https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Trigger-conditions-filling-the-information-gap/ba-p/731974

I have a flow where I would like a trigger condition where it is one of 4 different triggers. I have 4 fields in my SharePoint list that could update, so I have created 4 dummy fields that update when a change is made.

So I would like my trigger condition to be this:

if field 1 is not equal to dummy field 1

if field 2 is not equal to dummy field 2

if field 3 is not equal to dummy field 3

if field 4 is not equal to dummy field 4

The syntax is kicking me to the curb, and if anyone can lend a hand that would be great.

Here is my actual flow for clarity.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Expiscornovus 33,828 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
Hi @smorley,

You should be able to use this syntax. Replace the hard coded values 1,2,3 and 4 by your dummy fields.

@or(not(equals(triggerOutputs()?['body/field1'], 1))) @or(not(equals(triggerOutputs()?['body/field2'], 2))) @or(not(equals(triggerOutputs()?['body/field3'], 3))) @or(not(equals(triggerOutputs()?['body/field4'], 4)))

Was this reply helpful? Yes No
smorley 546 on at

Like (0)

Report
Copy link

Link copied!

Thanks @Expiscornovus - I was trying too hard with the syntax, trying to get it on one line. Although I may have not explained it right.
Let me try again.
Looking at my flow.
Trigger the flow:
if Unit name doesn't equal workflow unit name or Med Year doesn't equal workflow med year

I would like it to evaluate both at the same time.

Was this reply helpful? Yes No
smorley 546 on at

Like (0)

Report
Copy link

Link copied!

@Expiscornovus syntax is good now, but the flow still runs twice. Once when I make the change and it goes through the workflow and updates my list item, and then the second time where there were no changes.

Was this reply helpful? Yes No
Expiscornovus 33,828 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @smorley

A possible workaround could be to add a boolean field (with a default value of false) to your list which. Set that boolean to true when your change the item for the first time in your flow. And add a boolean equals false expression to your trigger conditions. That could prevent your flow from triggering twice.

Was this reply helpful? Yes No