Applies to Product - Microsoft Dataverse
What’s happening?
Customers are unable to override environment variables using the settings file during deployment in certain scenarios. Specifically, the expected environment variable values are not being set correctly after pushing the deployment.
Reason:
This arises when the current value of an environment variable is not removed from the solution before exporting. This behavior is by design, as the presence of a current value can prevent the settings file from overwriting it. Additionally, the default value may also interfere with the expected behavior.
Resolution:
- Ensure that the current value of the environment variable is removed from the solution before exporting it. This step is crucial for the settings file to overwrite the value as expected.
- If the default value is present, consider removing it as well before exporting solutions containing environment variables.
- When deploying the solution, if the upgrade option is used, and the current value has been removed, the environment variables should reflect the expected values. If not, redeploy the application without using the upgrade option to ensure the environment variables are updated correctly.