{"id":26920,"date":"2023-12-13T08:00:00","date_gmt":"2023-12-13T16:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/environment-variables-are-now-always-visible-and-editable-during-solution-import-and-pipeline-deployments\/"},"modified":"2025-06-11T07:42:59","modified_gmt":"2025-06-11T14:42:59","slug":"environment-variables-are-now-always-visible-and-editable-during-solution-import-and-pipeline-deployments","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/environment-variables-are-now-always-visible-and-editable-during-solution-import-and-pipeline-deployments\/","title":{"rendered":"Environment Variables are now Always Visible and Editable during Solution Import and Pipeline Deployments"},"content":{"rendered":"

We<\/span> have <\/span>just released <\/span>a change that <\/span>allows makers<\/span>, <\/span>who are using pipelines and solution import<\/span>, <\/span>to view and change the values of a solution\u2019s environment variables with any deployment.<\/span> Previously, we conditionally hid the environment variables if there was a value available for them. This created some confusion and ambiguity on how environment variables were obtaining their values and limited the environment variable update experience. Now, makers will be able to <\/span>validate<\/span> the values that are going to<\/span> be<\/span> used in their components <\/span>(<\/span>such as <\/span>their apps) <\/span>in the target environ<\/span>ment.<\/span><\/span>\u00a0<\/span>
\n\"solution
\nThis is a huge step forward for environment variables ease<\/span>–<\/span>of<\/span>–<\/span>use and transparency, so makers of all experience levels can <\/span>participate<\/span> in healthy ALM practices, <\/span>especially with <\/span>pipelines<\/span> which makes it all even easier<\/span>.<\/span> Each environment variable in the solution will have one of three value<\/span> sources<\/span> in this new experience<\/span>: <\/span>solution value, target environment value, or default value.<\/span><\/span>
\nSee for yourself today, now that the feature has been released everywhere!<\/span><\/p>\n

Coming soon: <\/span>a<\/span>utomatic <\/span>s<\/span>egmentation of environment variable values<\/span><\/span><\/h2>\n

Next month, the default experience will no longer export environment variable values in your solution. This makes it easier to follow best practices and avoid inadvertent mistakes. A new \u201cExport value\u201d toggle within the environment variable settings will allow you to opt-in to exporting the value, if needed.<\/span><\/span><\/span>
\n\"New<\/p>\n

\u00a0<\/p>\n

Paired with the new change during deployment, now environment variables will work transparently and as intended by your organization. Of course, if what you have now works for your use-cases, we won\u2019t be overwriting your existing environment variables\u2019 current behavior. But for every new environment variable created (or if you manually turn off the toggle), if you would like to dynamically change the values of your environment variables every time you import or deploy, you won’t have to clear the values since they will already be excluded!<\/span>\u00a0<\/span>
\nWe hope this recent change demystifies the inner workings of environment variables and enables more makers to use them in their solutions. Look out for the change next month too, enabling all makers to use environment variables with smart defaults that make it easier to follow best practices. As always, thank you to all the makers and admins who expressed passionate feedback that drove these improvements; we hear you!<\/span><\/p>\n

\u00a0<\/p>\n

Learn more about environment variables<\/h2>\n