Can we access environment variables inside Trigger condition

[johnjohn123]

Can we access environment variables inside Trigger conditions ? if not then how we can make the Trigger condition dynamic in a way that we can modify it without actually modifying the workflow? Thanks

[Matthy79]

Should work but be careful. Since a view months the change of an environment variable didn’t effect the flow (because during compiling the current value was stored into the flow). You had to turn off and turn on the flow to make it work again with the new value. This was changed by Microsoft, BUT if you change the value if an environment variable it takes a little to recognize the new value in all your flows (Usually not longer than one minute)

[johnjohn123]

@Matthy79 So you mean it is possible to reference environment variables inside Trigger conditions, as most links are saying that this is not supported yet.. such as this link https://powerusers.microsoft.com/t5/Building-Power-Apps/Use-an-Environment-Variable-in-a-Flow-trigge...  

[Matthy79]

Yes, I say it works. But there are a lot of triggers and Microsoft Power Plattform has a lot of bugs. Why do you ask this questions? It looks like you've tried it and it didn't work on your side. Please provide screenshots. I've tried it again 2 minutes ago with dataverse trigger and even changed the value of the environment variable and it worked with no problems.

The link you posted is from 2021 and the solution worked but they don't use it in the trigger condition but in the trigger itself. The person saying that it didn't work used it wrong and also not using it inside the trigger condition.

[LinnZawWin]

@johnjohn123 

As @Matthy79 mentioned, the thread that you posted was in 2021 and it was updated to be supported in 2022 Wave 1. 

https://learn.microsoft.com/en-us/power-platform-release-plan/2022wave1/power-automate/environment-v...

[johnjohn123]

@LinnZawWin ok so what is the syntax to get the environment variables inside Trigger Condition ? as i can not find it.Thanks

[Matthy79 · Accepted solution]

The syntax is exactly the same as everywhere else. The best way is to create a compose action and put in your condition there. After that you copy that condition, put it in the trigger condition and put an @ at the beginning of it.

Here is a sample: "@equals(triggerOutputs()?['body/emh_name'], parameters('Triggercondition (emh_Triggercondition)'))"

this is how it should look like: