Trigger condition with a not() is well not working!

(0) Share

Report

Posted on by westerdaled

672

I want to add trigger condition to flow that resides with a solution, in order to stop it retriggering .

I have added my expression to a compose action it there are not issues. When I add the same expression with the @ prefix to the trigger condition it errors

approval with trigger conditon.PNG

here is he expression

@not(equals(triggerOutputs()?['body/TestStatus/Value'], 'Terminated'))

By are process of elimination it appears the not() expression is the issue , even in this simple test which also fails with the same error .. er am I missing something here?

When an item or file is modified.PNG

Categories:

Building flows

All responses (6)

Answers (1)

Sort by

annajhaveri 8,531 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
@westerdaled what is the data type of the Test Status column? There seems to be some issue with the expression, it should be similar to below expression

@not(equals(triggerbody()?['TestStatus']?['Value'],'statusvalue'))
westerdaled 672 on at

Like
a
(0)

Report
Copy link

Link copied!

@annajhaveri thanks for your reply it is a SharePoint choice field . I will give your sugestion a try shortly.

I placed my orignal expression a Compose and to got no issues . Also it doesn't even work with string comparison which concerned me.
westerdaled 672 on at

Like
a
(0)

Report
Copy link

Link copied!
@annajhaveri

I have an update for you, and I think I have found a bug in Power Automates which I guess we might to push up the chain to the dev team.

Just to recap , in my Modified or Created Trigger flow, I don't want it to run if a choice column value shows 'Terminated'

In my Trigger Condition I have

@not(equals(triggerOutputs()?['body/TestStatus/Value'], 'Terminated'))

They syntax is fine, as proven when I replicate this a compose action. However, the flow fails with

Now I change my test string to something else

@not(equals(triggerOutputs()?['body/TestStatus/Value'], 'GoneFishing'))

Flow runs fine: Go figure🙄

In my case I will changing 'Terminated' to 'Closed' and see if the trigger condition doesn't get upset about that.
Verified answer

annajhaveri 8,531 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@westerdaled i did try to use your trigger condition which compares Terminated value and it works. Could you try creating a new flow and see if it has same issue?
westerdaled 672 on at

Like
a
(0)

Report
Copy link

Link copied!

Ok I have now tested 'Closed' which works but I will create another flow outside my solution and repeat with ' Terminated' .. Then I better get on with my remaining bug fixes.😁
westerdaled 672 on at

Like
a
(0)

Report
Copy link

Link copied!

@annajhaveri

I now know that condition with 'Terminated' which is an issue only when I try to Test my automated flow in the edit mode.

I don't get the issue when I simply change one the list item property values or change the condition to 'Closed' in the edit mode above .. So there is a minor bug but not a show stopper as I first thought.

The Power Automate is now in production and I have tested it with a 'Terminate'
Thanks for helping me with this issue.