cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Django
Impactful Individual
Impactful Individual

Updating Environment Variables in Managed Solution

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?

5 ACCEPTED SOLUTIONS

Accepted Solutions

Yes @riclund2 : unmanaged solution have more options but this post is explicitly for the managed solutions because that is the way to go for my desired Application Lifecycle Management purpose through different environments and different tenants. That is the whole purpose of Environment Variables with a separated Default Value from an optional overwritable Current Value.

 

Here is an update after a lot of troubleshooting with Microsoft Support.

Basically when exporting a managed solution from an unmanaged solution with environment variables there are three scenario's:

  1. the unmanaged solution never had a current value and then you exported to a managed solution.
  2. the unmanaged solution has a current value and you removed the current value before you exported to a managed solution. This seems to be the best practice according to Microsoft: Use environment variables in solutions - Power Apps | Microsoft Docs
    Dataverse_Environment_variables_values.png
    Microsoft seems to have changed this documentation since I raised a support ticket --> it used to say we should remove the Current Value so a red banner would prompt stating an Environment Variable needs to have a value. 🤔
  3. the unmanaged solution has a current value and you left that current value intact before exporting to a managed solution

We have run through every option to try to change the Current Value in every scenario in totally new target environments without errors:

  1. edit through modern interface of managed solution
  2. edit through Advanced Find of Power Platform Environment
  3. edit through modern interface of default solution
  4. edit through Dataverse / Common Data Service backend Tables / Entities
  5. edit through unzipping managed solution, editing solution files and rezipping to managed solution

 

I do not want this to make a whole new documentation page so here is my conclusion:
Microsoft Product Team is fixing a bug because option 1 should also work in every scenario.
However for now:

If you want it to work in the modern interface without a lot of hassle: use scenario C above because then you can use option 4 to edit the Current Value
If you are like me and followed Microsofts advise, using scenario B & you added a totally new Current Value for the first time right after import into target environment. There may be moment where you want to update the Current Value for a second, third etc time. The only working workaround I found is to change the unmanaged solution to scenario C by adding the Current Value back in a new exported version of the managed solution. Unzip this new managed solution, edit the environment_variable_values.json to match the desired values AND the correct Environment Variable Value record GUID of the target environment and then import the new managed solution into the target environment. Now it will accept the import and change the current value.

View solution in original post

Found another solution. Just move all the environment variables to another solution and export and import that solution as unmanage. That way your workflows are still managed, and the environment variables can be changes as required.
Not a perfect solution, but it works.

View solution in original post

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

View solution in original post

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 

View solution in original post

62 REPLIES 62
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @Django,

You don't need to clear the default value or values before exporting as managed. When you import into the target environment via make.powerapps.com or make.preview.powerapps.com, it will prompt you to set the value at import time and then should import successfully. 

Hope this helps!

Yes @EricRegnier , that was the behavior that I have seen many times... but in my last export this monday of a managed solution and even when importing it in a totally new environment / totally different tenant (all Europe though) this behavior has changed....

See [BUG]: Edit Environment variable from managed solution · Issue #591 · microsoft/powerapps-tools (git... for troubleshooting details thus far...

EricRegnier
Most Valuable Professional
Most Valuable Professional

I just tried exporting as managed without removing the value and re-importing in another environment and it’s working for me. I’m in the crm6 region. Retry, perhaps the issue is fixed now?

Hi @EricRegnier  I created a video to explain better and show my full experience -->

See (55) Power Platform Solution Environment Variable Bug - YouTube

the video is a few minutes long but shows how My Custom Solution is behaving in a fresh trial environment and I see the same behavior in other Solutions like the CoE starter kit:

 

  • Current Value cleared from Unmanaged Solution before exporting to Managed Solution
    This is described as the best practice at Use environment variables in solutions - Power Apps | Microsoft Docs

    so the red banner popup should appear after a fresh import informing the person importing that an Environment Variables needs a value

  • no red banner popup to add Current Values after fresh environment first import
    ==> Functionality missing
  • need to use Default Solution to add Current Value
    ==> Workaround
  • after adding Current Value no way to edit
    ==> major flaw because this is why Environment Variables are better than creating custom entities with variables to manage in solution
EricRegnier
Most Valuable Professional
Most Valuable Professional

Cheers for the awesome video. Seems like you did find a workaround via the default solution though, that's good to know. You can also try through the classic solution explorer and Advanced Find. It should let you edit it from there as well.

Using the Default Solution seems to work sporadic. On day of import it seems to work fine but a few days later:
Django_0-1606727016356.png
So this workaround is not very reliable.

 

Using the Classic Solution explorer, is not possible for Environment Variables right?

Django_1-1606728063423.png

So no edit if there is no Component in Classic Experience for Environment Variables.

 

Using the Advanced Find through the Model Driven App button

Django_2-1606728217784.png

just opens up the default Model Driven App trying to edit specific entity:

Django_3-1606728252458.png

So same barrier here...

@Django where did you get to with this? I'm hitting the exact same issues. I assume putting the EnvVars into a separate unmanaged solution is the way - about to try that. Seems like this functionality is pretty rough around the edges...

For anyone coming after, an unmanaged solution does work, although ideologically it's not ideal as we prefer everything outside dev to be managed. Anyways it brings them in and allows them to be edited during import and adjusted after. Unless I'm missing something (very possible!) this is a much more realistic setup.

Yes @riclund2 : unmanaged solution have more options but this post is explicitly for the managed solutions because that is the way to go for my desired Application Lifecycle Management purpose through different environments and different tenants. That is the whole purpose of Environment Variables with a separated Default Value from an optional overwritable Current Value.

 

Here is an update after a lot of troubleshooting with Microsoft Support.

Basically when exporting a managed solution from an unmanaged solution with environment variables there are three scenario's:

  1. the unmanaged solution never had a current value and then you exported to a managed solution.
  2. the unmanaged solution has a current value and you removed the current value before you exported to a managed solution. This seems to be the best practice according to Microsoft: Use environment variables in solutions - Power Apps | Microsoft Docs
    Dataverse_Environment_variables_values.png
    Microsoft seems to have changed this documentation since I raised a support ticket --> it used to say we should remove the Current Value so a red banner would prompt stating an Environment Variable needs to have a value. 🤔
  3. the unmanaged solution has a current value and you left that current value intact before exporting to a managed solution

We have run through every option to try to change the Current Value in every scenario in totally new target environments without errors:

  1. edit through modern interface of managed solution
  2. edit through Advanced Find of Power Platform Environment
  3. edit through modern interface of default solution
  4. edit through Dataverse / Common Data Service backend Tables / Entities
  5. edit through unzipping managed solution, editing solution files and rezipping to managed solution

 

I do not want this to make a whole new documentation page so here is my conclusion:
Microsoft Product Team is fixing a bug because option 1 should also work in every scenario.
However for now:

If you want it to work in the modern interface without a lot of hassle: use scenario C above because then you can use option 4 to edit the Current Value
If you are like me and followed Microsofts advise, using scenario B & you added a totally new Current Value for the first time right after import into target environment. There may be moment where you want to update the Current Value for a second, third etc time. The only working workaround I found is to change the unmanaged solution to scenario C by adding the Current Value back in a new exported version of the managed solution. Unzip this new managed solution, edit the environment_variable_values.json to match the desired values AND the correct Environment Variable Value record GUID of the target environment and then import the new managed solution into the target environment. Now it will accept the import and change the current value.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (4,836)