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
Django
Impactful Individual
Impactful Individual

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

Jaco_Campher
Advocate II
Advocate II

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

EricRegnier
Most Valuable Professional
Most Valuable Professional

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

61 REPLIES 61
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!

Django
Impactful Individual
Impactful Individual

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?

Django
Impactful Individual
Impactful Individual

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.

Django
Impactful Individual
Impactful Individual

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...

riclund2
Advocate I
Advocate I

@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...

riclund2
Advocate I
Advocate I

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.

Django
Impactful Individual
Impactful Individual

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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Users online (3,345)