You’re offline. This is a read only version of the page.
last month , i went to all the environment variables inside my Dev environment's solution and i set their Export checkbox to No. but today i check those settings since i added a new environment variable, and i noted that all the solution environment variables inside my Dev environment have their Export checkbox set to Yes, as follow:-
any advice why those were changed automatically for me? now i want to set them to No, because i want to export the solution from Dev to PROD environment. any advice why this happened and how i can avoid ti in the future?
@johnjohnPter That makes sense now.
When you explicitly add an Environment Variable to a solution in the maker portal, you get this dialog which prompts you to select whether you wish to include the current value of the Environment Variable into the solution (as well as it's definition). If you choose to include the current value, then it seems that the 'Export Value' flag on the Environment Variable definition is automatically set to Yes
So it seems that the 'Add Required Objects' option is including the Environment Variable into your solution using this option by default because your App has a dependency on the Environment Variable.
As a general rule of thumb, I recommend to never use the 'Add Required Objects' option. Because this option detects all objects that your existing solution components are dependent upon and includes them into your solution. As a best practice, you should only ever include your custom objects (unmanaged) that you have created from scratch or any managed objects that you have customised into your solution. Otherwise you run the risk of very complex solution layering, merge conflict and deployment issues when your solution is deployed to downstream environments.
@parvezghumra i were able to replicate the issue, if i went to the power apps inside the Dev environment, and select to "Add required objects":-
seems this step will reset all the Export check-boxes and set them to Yes.
@Velegandla still showing at my end
Update:
It seems the Export Value option has been removed.
====================================================
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
https://www.linkedin.com/in/devendravelegandla/
@johnjohnPter Apologies for the delay in following up.
I've been unable to replicate this behaviour in my tenant. So I would recommend either trying to investigate what's causing this anomaly in your environment, or otherwise raise a support request with Microsoft to have them investigate
I verified in my Tenant, it stays the same though i cleared the values for current Site and List.
I will add the values back and wait or 24 hrs to update this thread again.
====================================================
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
https://www.linkedin.com/in/devendravelegandla/
@parvezghumra were you able to replicate this?
@parvezghumra thanks
@johnjohnPter in that case my guess is that the platform is doing this automatically when you export a solution containing environment variables. I will test this in my own environment tomorrow to confirm and let you know
@parvezghumra no one have this permission, except my account. also this happened today, after i set all check-boxes to No yesterday
#1
bscarlavai33
5
Super User 2025 Season 1
#2
Michael E. Gernaey
4
Super User 2025 Season 1
#3
Vince_K
2
Share
Report
All responses (
Answers (
