cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MarrinerDev
Advocate III
Advocate III

Environment Variables section not showing in Dynamic Content

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.

17 REPLIES 17
Expiscornovus
Super User
Super User

Hi @MarrinerDev,

 

Looks like you are taking all the corrects steps and I would have expected that the environment variable would have been there.

 

Couple of things to be aware of with environment variables.

- It could be that the section is still called Parameters instead of Environment Variables, they only recently rebranded it.

- Environment variables would be filtered by data type in the near future. You might want test with a compose action. But I assuming you did because it doesn't work with any action.

https://docs.microsoft.com/en-us/powerapps/maker/data-platform/environmentvariables#current-limitati...

 

I have tried reproducing your steps. But unfortunately I am unable to reproduce your issue.

 

Just for your information I will share those steps. Might help with the troubleshooting.

 

1. Created a environment variable & cloud flow in the same solution and environment (default environment).

 

solution_overview.png

2. Text data type, only default value.

 

somename_environmentvariable02.png

 

3. Create a cloud flow and searched for the new variable in the dynamic value section.

 

defaultenvironment.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #PowerVirtualAgents content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


rhousham
Frequent Visitor

I too am experiencing this problem. I'm going to try and delete the solution and try again but it doesn't seem to work as it should.

carl1to
Resolver I
Resolver I

Same problem here. Somehow this "Environment Variable Section" disappeared for me. Even it is working in existing flows it doesn't show up in ne flows or even new solution with cloud flow created directly inside the solution....

maxpower45255
Advocate II
Advocate II

Did you try publishing your customizations? I have an even weirder issue. I added a few environment vars and published changes. I can see them in one of my flows' dynamic content but not in the other. I refreshed the page several times to no avail. hmmm. 

carl1to
Resolver I
Resolver I

on the next day, it worked just fine... probably needed to refresh the browser tab or something...

Django
MVP

Is there some delay before an Environment Variable becomes available in Dynamic Content of Flow?

Just added on, I can see it in the Environment Variable Definitions as well as in the Environment Variable Values tables but not (yet??) in Dynamic Content of an existing flow...

Django
MVP

Even stranger: 

Flow that existed before new Variable was created:

Django_0-1647776197824.png

New Flow after Variable was created:

Django_1-1647776238129.png

 

maxpower45255
Advocate II
Advocate II

@Django I've seen this issue happen but not always. The solution I've found is is to turn off and turn the flow back on. Another trick I found is to prefix all my environment variables with a few letters so it's easy to find them when I search for them.  

Good luck

Django
MVP

Thanx @maxpower45255!

I tried disabling and enabling the flow again but no luck...

Saving a copy of the flow and adding the copied flow to solution seems to work for the copy --> but original flow should see the variable so that is what I am aiming for 🤓

maxpower45255
Advocate II
Advocate II

@Django Try publishing your customizations, along with turning the flow off/on. Outside of this, you may need to wait a few minutes. These are some of the quirks of Power Automate that I can't explain. I hope someone from the MSFT product team can pitch in and hope they resolve this odd behavior. 

 

Can confirm that publishing customizations and turning on/off worked for me.

One of those many quirks.

Thanx @maxpower45255, I just waited a few days and it suddenly started appearing in pre-existing flows.

If @Jsalaz1989 confirms that Publishing customizations AND Turning flow on/off forces the flow to automagically start showing newly added  Environment Variables than that are valuable insights 💪👍

hinke
Regular Visitor

I saw similar behavior after changing the Current Value of an environment variable.
After changing the value and publishing the customizations, the Flow action that used the Environment Variable from the Dynamics Content, still displayed the old value, while a List action in the same flow that retrieved the current value from the "Environment Variable Values" entitity showed the updated value.

After turning the Flow off and on again, the updated value was also displayed correctly in the step  that used the environment variable from the Dynamic Content.
So it looks like the value of an environment value in the Dynamics Content is cached and not immediately updated when the value on the entity is updated.

This really should be fixed as soon as possible in my opinion. Part of the benefit of Environment Variables is that you can set the in the release pipeline. 
But when you set updated values for Environment Variables in your ACC and PROD environment in your release pipeline, then the new value should active  immediately, without having to turn all your flows off and on again.

Can we expect a fix for this? 

asanthiyagu
New Member

I was facing the same issue when I open the flow from "My Flows" section. When I edit it from solution it was appearing.

aarnav
Advocate I
Advocate I

I had the same issue and turning the flow off and back on resolved the issue for me.

Vitss
Advocate II
Advocate II

I do encountered the same behavior while making a new Flow (2nd in a solution where the environment variables are working fine in Flow and Powerapp).

'Solved' the issue by skipping the first screen for choosing name and trigger and selected the trigger and name afterwards.

Can confirm this "workaround" -- MS does some daft, head-scratching things from time to time... Thanks, @Vitss!

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (4,157)