Difference between revisions of "Environment Variables"
| Line 3: | Line 3: | ||
== General == | == General == | ||
Environment Variables can return a value based on the environment the requesting application is in. | Environment Variables can return a value based on the environment the requesting application is in. | ||
| − | EnvVars are solution aware and can therefore be "transported" with a usual Deployment (see [[ALM | + | EnvVars are solution aware and can therefore be "transported" with a usual Deployment (see [[ALM]]). |
{{ | {{ | ||
Revision as of 17:05, 19 December 2021
Environment Variables (EnvVars) can be used to retrieve a value based on the current environment.
General
Environment Variables can return a value based on the environment the requesting application is in. EnvVars are solution aware and can therefore be "transported" with a usual Deployment (see ALM).
Be aware
Local values should not be included in a solution. Otherwise, it will be impossible to override the value in a downstream environment.
Structure
EnvVars are built with two tables:
- Environment Variable Definition
- Environment Variable Value
Environment Variable Definition
As the name suggests posts in this table contain the definition of an environment variable. This contains
- DiplayName
- SchemaName
- Description
- Data Type
- Default Value
Environment Variable Value
Also called "Local Value". A post in this table is always related to some definition and should never be included in a solution. It overrides the default value of a definition and is the value of the current environment.
Use case
Use cases could for example be
- URL's
- Canvas App Ids
- Record Ids
- Switches
- Connections
- Other Configuration
How to create
Environment Variables are, as mentioned, Solution components and should be created from a solution as well. First, the definition has to be created. After you save the first time you can add a local value. This local value should then be removed from the solution (via the ... besides it).
How to use
Power Automate has a native integration with EnvVars. All the available EnvVars will be shown in the list of dynamic values.
Be aware
If you use this approach EnvVars are cached. When you change the value you have to turn all the flows off and on to get the new value.
If you would like to use EnvVars in any other way (Plugins, JS, ...) you have to handle them yourself. This means getting the rows and deciding whether to use the default or local value.
History
- 2019-11-04 - Announcing public Preview (MS announcement)
- 2020-09-15 - Announcing GA and new Solution import experience (MS announcement)
- 2021-04-14 - Announcing Type Data Source (MS announcement)
- 2021-08-19 - Announcing public Preview of Environment Variables Support in Power Platform Build Tools (MS announcement)
- 2021-12-15 - Announcing GA of Environment Variables Support in Power Platform Build Tools (MS announcement)
Related Content
PowerWiki
Microsoft Resources
- Use Environment Variables
- Import Solution Task of Power Platform Build Tools
Community Content
- Environment Variables in Power Automate by Pieter Veenstra
- Now it is time to be Curious about Power Platform Environment Variables! by Jens Kofod
- Power Platform Data Source Environment Variables by Rebekka Aalbers
- Using Environment Variables in Dynamics 365 CRM – Part 1 by Inogic
- Tip #1363: Get Environment Variables in Power Automate (and Power Apps) by CRM Tip of the Day
- Dataverse CustomAPIs to get EnvVar Value by David Rivard