Environment Variables section not showing in Dynamic Content

[MarrinerDev]

I'm testing using environment variables in a Flow and when I try to reference the environment variable in a Flow, the "Environment Variables" section in the Dynamic Content panel is not showing up at all.

I've set up a very simple example of a string environment variable called "SomeName". I then select the solution and click add new cloud flow. For the sake of argument, I create a new flow started from PowerApps.

When I add any action under that initial step and try to set a value for any settable field in that action based on the environment variable I can't because the "Environment Variables" section doesn't show up in the Dynamic Content panel.

Any ideas why or what I'm missing?

I created a test canvas app in the same solution and the variables are visible there (albeit via the ridiculously cumbersome Dataverse table approach).

Many thanks.

[Anonymous]

Turning on and off worked out for me. Thanks

[Digi365de]

Sometimes saving the flow once and refreshing the page helps if you created the flow directly form the solution panel.

[Digi365de]

I have the same problem too. Driving me nuts. It seems that in the flow I created a couple of months ago the environmetn variable doesn´t show up and even doesn´t work if I copy paste the value into in variable and it shows in this brown lable/icon. the flow than gives an error:

Unable to process template language expressions in action 'Initialize_variable_-_ApprovalsApprover' inputs at line '0' and column '0': 'The workflow parameter 'emlApprovalRequestor (hal_emlApprovalRequestor)' is not found.'.

Super annoying.

[mgr]

That drove me nuts as well.
Had an issue with environment variables used in dataverse trigger after copying the expressions form another flow.
It was always showing "Fix the trigger" and I couldn't choose env vars from sidebar.

But now I found the workaround (successfully applied for 6 flows):

turn off
(maybe refresh page or wait some 5 minutes)
click "edit", not "fix the trigger"
verify that env vars are visible now and use them as to your needs
save flow
go back into flow metadata
turn on by ignoring "fix the trigger"
refresh flow metadata page
=> "fix the trigger" is finally gone

[Anonymous]

Editing the cloud flow directly from the solution manager worked for me as well.

[Django]

Same experience as Greg...

Apparently opening the Flow from My Flows in Power Automate Portal could cause Environment Variables to not render. Opening the Flow from the Solution should give a URL like

https://make.powerautomate.com/environments/[EnvironmentID]/solutions/a62ccaee-86ed-ed11-8848-000d3a... and here all Environment Variables started rendering again for me...

[ArpanShah]

Hi,

Responding to old thread, but solution is clean browser cache. 

Somehow Power automate cache these values and showing from there only, either you open a new browser instance or clear browse cache.

Hope this helps.

Arpan Shah

[ChristianHb]

Try to open the flow from a solution. Environment variables are shown.

If I opened the flow from tab "My flows", environment variables are not shown.

[abm]

Hi @ChristianHb 

Environment variables are accessible only via solutions.

Thanks

[Emmytau]

I can confirm that this is still an issue in December 2023, and that publishing all customizations works to solve it. 

[jisnard]

Switching back to classic designer did the trick for me (after an hour of turning on and off and publishing the customization and refreshing my browser, none of which working)...

[carlblunck]

Hi all - a colleague of mine told me that you need to place the flow within a solution for that flow to then pickup the environmentvariables created through another solution.  Did this and can confirm it made the environmentvariable appear.  Didn't need to turn the flow on/off or anything else.

Cheers

Carl