web

You’re offline. This is a read only version of the page.

Power Platform CommunityForums Power Automate Trigger Condition not ...

Power Automate

Unanswered

Trigger Condition not working when combining not and equals

(0) Share

Report

Report

Posted on by anatius007

2

Dear Pros,

I am trying to use the following trigger condition

@not(equals(triggerBody()?['StatusOfDocumentationOld'],triggerBody()?['StatusOfDocumentation']?['Value']))

to compare to values and only fire when they are not equal.

However, I am always getting

Unable to get property 'properties' of undefined or null reference

as an error message. Both values exist and once I remove the not from the condition, it works fine...

Any idea what I am doing wrong is highly appreciated.

Many thanks!

Christian

Categories:

I have the same question (0)

All responses Img

All responses (3)

Answers Img

Answers (0)

v-bacao-msft on at

Like (0)

Report
Re: Trigger Condition not working when combining not and equals

Hi @anatius007 ,

I used the same expression on my side for testing. When I saved Flow, I didn't encounter similar problems.

Maybe you can try the following expression:

@equals(equals(triggerBody()?['StatusOfDocumentationOld'],triggerBody()?['StatusOfDocumentation']?['Value']),false)

Best Regards,

Was this reply helpful? Yes No
anatius007 2 on at

Like (0)

Report

Re: Trigger Condition not working when combining not and equals

Hi Barry,

Thanks for your suggestion, but your proposed expression gives the same error message as my original one...
Any other ideas?

Regards,
Christian

Was this reply helpful? Yes No
v-bacao-msft on at

Like (0)

Report

Re: Trigger Condition not working when combining not and equals

Hi @anatius007 ,

It's strange that these trigger conditions work fine on my side.

Have you tried re-creating the Flow and updating the connection?

Or use other fields to test the not() function.

Besides, you could consider using Condition instead of trigger conditions.

Best Regards,

Was this reply helpful? Yes No

Join the conversation