web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Environment Variables ...
Power Automate
Unanswered

Environment Variables section not showing in Dynamic Content

(0) ShareShare
ReportReport
Posted on by

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.

Categories:
I have the same question (0)
  • Expiscornovus Profile Picture
    33,189 Most Valuable Professional on at

    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-limitations

     

    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

  • rhousham Profile Picture
    8 on at

    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 Profile Picture
    208 on at

    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 Profile Picture
    223 on at

    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 Profile Picture
    208 on at

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

  • m3ngi3 Profile Picture
    725 on at

    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...

  • m3ngi3 Profile Picture
    725 on at

    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 Profile Picture
    223 on at

    @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

  • m3ngi3 Profile Picture
    725 on at

    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 Profile Picture
    223 on at

    @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. 

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard