Stuck with trigger conditions

[Lefty]

Hi

I had a working flow which would run when an item is created or modified and I'd added a trigger condition to ensure the flow did not run when my service account had created the item or made a change:

@not(equals(triggerBody()?['Editor']?['Email'],'emailaddress')) 

I now have a requirement where I do not want the flow to run when the above email is true AND when the status column in my SP list is set to partially complete. I added the following on another line but the flow triggered, which prompted me to read "Specify one or more expressions which must be true for the trigger to fire.":

@not(equals(triggerBody()?['Status'],'partially complete'))

I'm not sure how I combine both conditions and if my syntax is correct for the 2nd trigger anyways?

[Naveen_772 · Accepted solution]

Hey @Lefty ,

First of all, I would suggest first adding the expressions to the compose action just after the trigger to make sure the output you're receiving from the expression is boolean or not.

If the output is correct then copy the expression and paste in trigger condition. Make sure to remove the curly braces from expression in trigger condition.

For example,

Expression in Compose:

@{and(not(equal(1,2)),equal(1,1))}

Expression in Trigger Condition:

@and(not(equal(1,2)),equal(1,1))

Regarding the combining of the expression, try using the and function.

In your case:

@and(not(equals(triggerBody()?['Editor']?['Email'],'emailaddress')),not(equals(triggerBody()?['Status'],'partially complete')))

To me, your second expression looks correct. Still, I would recommend adding it to compose to check it out.

If my post helps, then please consider Accept it as the solution to help the other members find it more quickly. 

[Lefty]

Hi @Naveen_772 

Thanks for your response.

I have tried your advice and done the following:

Created a new flow, trigger is 'when an item is created or modified' (SP)

Added a compose action and pasted in the following as an expression:

@not(equals(triggerBody()?['Editor']?['Email'],'email'))

When I click ok I get an error the expression is invalid.

This is odd as this expression worked fine for me under the trigger conditions, this is what I tried in the compose expression:

@not(equals(triggerBody()?['Editor']?['Email'],'email'))

{not(equals(triggerBody()?['Editor']?['Email'],'email'))}

@{not(equals(triggerBody()?['Editor']?['Email'],'email'))}

All 3 are not acceptable for flow... what am I doing wrong at the first step please?

[Naveen_772]

So if you are pasting it in the expression section you need to get rid of @ and curly braces.

In your case:

not(equals(triggerBody()?['Editor']?['Email'],'email'))

Just paste the above expression in the expression section and click "OK".

[Naveen_772]

Hey @Lefty 

Please let me know if you need any further help.

If I am able to resolve your query then please Mark my post as a solution!😊

If you liked my response, please consider giving it a Thumbs Up. 👍

This will help other community member finding the solution quickly.

Regards

Naveen

[Lefty]

Thanks so much for explaining although I have followed all the steps something is wrong please see my trigger conditions below. I thought it was working until I submitted a new SP item and the WF should have triggered as both conditions were false in the scenario, i.e. my Service account was not the user and the status was not partially complete:

@And(not(equals(triggerBody()?['Editor']?['Email'],'ServiceAccountEmail')),not(equals(triggerBody()?['Status']?['Value'],'partially complete')))

But the WF has not triggered.

[Lefty]

@Naveen_772 

Ignore the last message, it triggered after a long time!

I am just testing a few more scenarios, but so far so good. I will let you know shortly, or will mark as answered

Thanks

[Lefty]

@Naveen_772 

Sorry, need help with 1 more please, how do i extend the condition to include 2 different status values. I.e. if the status is 'partially complete' or if status is 'nearly complete'. I tried this but the expression is wrong:

and(not(equals(triggerBody()?['Editor']?['Email'],'ServiceAccountEmail')), equals(triggerBody()?['Status']?['Value'],'partially complete') Or equals(triggerBody()?['Status']?['Value'],'nearly complete')))

[Naveen_772]

@Lefty ,

You are almost there just a quick change is needed. Or is a function, not an operator. You need to pass the parameters to it.

For example:

@and(not(equals(1,2)),or(equals(1,2),equals(1,1)))

In your case:

@and(not(equals(triggerBody()?['Editor']?['Email'],'ServiceAccountEmail')), or(equals(triggerBody()?['Status']?['Value'],'partially complete'), equals(triggerBody()?['Status']?['Value'],'nearly complete')))

I hope this helps.

[Lefty]

Thanks the expression is correct, but after all this, the workflow is still not doing what I need it to. Even though I have set the trigger condition to the above recommendation. the WF still triggers and changes the items, when it shouldnt as the 2 conditions were not met.

Please correct me if I am wrong in my understanding of what this condition means:

@And(not(equals(triggerBody()?['Editor']?['Email'],'ServiceAccountEmail')), or(equals(triggerBody()?['Status']?['Value'],'partially complete'), equals(triggerBody()?['Status']?['Value'],'nearly complete')))

I am asking it to not trigger if my serviceaccount email is equal to the email and if the status is equal to either partially complete or nearly complete?

As the the test I have just run, the service account was not the account being used, and the status was not either partially complete or nearly complete, yet the WF still ran.... any ideas?

Thanks

[Naveen_772]

@Lefty I think this will be the last piece of the puzzle.

As you mentioned you don't want to trigger the flow if the status is either "Nearly Complete" or "Partially Complete". But in the expression, we are only checking for the true case. You need to add the not function.

Expression: 

@And(not(equals(triggerBody()?['Editor']?['Email'],'ServiceAccountEmail')), or(not(equals(triggerBody()?['Status']?['Value'],'partially complete')), not(equals(triggerBody()?['Status']?['Value'],'nearly complete'))))

True case for the expression:

Email- Anything, except ServiceAccountEmail

Status- Anything other than partially complete or nearly complete

[Lefty]

Hey @Naveen_772 

Thanks

but I wanted the trigger to be triggered when its nearly complete or partially complete, hence why i removed the not from the expression, and I genuinely thought that was it - but oddly it still triggered, so I am missing something

[Lefty]

@Naveen_772 

Let me test some things out, i think the issue was a typo on my part