Updating Environment Variables in Managed Solution

[Django]

Documentation (Use environment variables in solutions - Power Apps | Microsoft Docs) states that we should remove Current Value of Environment Variables before exporting an Unmanaged Solution to a Managed Solution --> this will provide a popup during Managed Solution Import to enter the Environment Variable.

How can an Environment Variable Current Value be updated after import?

1. In the Modern Interface it states 
   This environment variable definition cannot be edited because it is in a managed solution.
2. In the CDS Data / Dataverse Table it states
   You do not have permission to access these records. Contact your Microsoft Dynamics 365 administrator for help.

I also mentioned this to the Center Of Excellence Starter Kit creators because there I see that Environment Variable Current Values behave in the same way when trying to update existing Environment Variable Values: [BUG]: Edit Environment variable from managed solution · Issue #591 · microsoft/powerapps-tools (git...

Anyh other ways that we can edit the values of these variables when imported as Managed Solution?

[ingovals]

@Django 

You are doing work that Microsoft should be doing. You should send them a invoice.

[_follone]

Hello everyone, I know that the topic is old, but this solution did not work for me, I believe it has become simpler to do, but still in my opinion not as it should.

I was in the same situation as you, I tried the recommended solution, but since the object exists in the target environment, it did not allow me to change the value in any way other than following these steps

No matter what your scenario is, this will work:

In the same environment as the managed solution with the environment variables exists you can:

Option 1:

1.1 - Create a temporary unmanaged solution

1.2 - Add existing environment variables you need to change the values for this temp solution

1.3 - Change the value and save the changes

After about 5 minutes the changes take effect and you can delete the temp solution from that environment.

Option 2:

2.1 - Create a solution patch in the environment where it is unmanaged

2.2 - Add existing environment variables in the patch

2.3 - Edit the variables and remove the solution values

2.4 - Export the patch in a managed way

2.5 - Imports into the target environment

After that you can delete the patch from the target environment or later import an update as an upgrade to the solution, that way the patch will disappear.

Important: Do not deploy option 2 through Power Platform Pipelines because it will not give you the option to update the variable, DO IT MANUALLY.

[Guillaume_G · Accepted solution]

I have just tried option 2 and it didn't update the target environment for me. So I had to use option 1 which worked perfectly.

Option 1:

1.1 - Create a temporary unmanaged solution

1.2 - Add existing environment variables you need to change the values for this temp solution

1.3 - Change the value and save the changes

[EricRegnier · Accepted solution]

I do the same steps @Guillaume_G listed. Or in more automated scenarios with CI/CD, I set the environments with the deployment settings file: https://learn.microsoft.com/power-platform/alm/conn-ref-env-variables-build-tools 

[trice602]

@Django - thanks for posting!  This works for me 🙂

(154) Update the Current Value of an Environment Variable in Power Platform Solutions - YouTube

Is it safe to say the way it is supposed to work is if I export my solution from Dev to Prod with no current values as a managed solution it should PROMPT AGAIN for a new variable value just like it does the very first time importing OR actually accept and post new current variables to Prod?

[Django]

Hi @trice602,

Only if:

• Current Value in your solution is empty
• Default Value in your solution is empty
• Target Environment does not have a Value for the Environment Variable

the prompt will happen.

So if you just import an updated version of your solution package in an environment that already knows a value for the variable, the prompt will not (re)appear…

[trice602]

Thanks again.  The issue that I was having an issue with was after the initial managed solution was imported, that target environment has a variable that will not update based on documentation; but your 2:51 video resolved this issue today! ⭐⭐⭐⭐⭐

[bfaye78]

It is possible to update the environment variables using XRM Toolbox Environment Variables Manager

[bfaye78]

It is possible to use XRM Toolbox Environment Variables Manager

[Paul31]

I experienced what I believe is the same problem today and the solution was surprisingly simple as I wasn't being prompted during import.  After clearing out the environment variable in the unmanaged solution and re-importing into the managed solution, there was a message/link to update the variable on the Solution Status Overview card of the solution Overview page.