Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

In case you imported a Dataverse solution in the past, you might have observed that, during the solution import, the Environment Variable doesn’t appear in the configuration options if it already has a ‘Default Value’ set.

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 validate the values that are going to be used in their components (such as their apps) in the target environment. 

Each environment variable in the solution will have one of three value sources in this new experience: solution value, target environment value, or default value.

Also, in the upcoming release, 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 “Export value” toggle within the environment variable settings will allow you to opt-in to exporting the value, if needed.

This new feature will not impact existing environment variables’ 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.

Refer the official blog post here

🙂