Environment Variables not coming with Pipelines

[mdenn]

I set up pipelines recently and noticed that my environment variables in my solution aren't properly coming over when deployed.  These are new variables that I haven't used before.  There wasn't a prompt for them when doing the deployment.  I don't see the variables listed in the target environment's Dataverse table for those.  When I click on the environment variable inside the solution, I get an error page.

Edit: I was wrong about them not coming over.  The error when I click on them still seems to be an issue though, but maybe a known one.  This question can be deleted.

[Thoman]

I too just got the Power Platform Pipelines enabled to be used with Solutions. I have three environments. Dev, Test and Production. I added an environment variable in my DEV environment with a default value (What I want to use when in production) and an override value (to use while developing and testing). When I publish to TEST. I would like to use a different value in that environment to do a broader testing but not the same value as Production or DEV. However, I don't get a prompt or an option to change it when I promote the environment up with Pipelines.

[mdenn]

You probably need to remove the value from the solution.  It is in the options on the side.

My issue came from that a coworker accidentally deleted some environment variables I was using.  I tried to recreate them in the Dataverse tables, but apparently there is more background wiring up that had to be done.  That was why I was getting an error.  I had to recreate new environment variables and switch everything to use those ones instead.

[Thoman]

Yeah... saw that... silly you have to remove the "Environment Overrides" though. It should happen automatically when publishing to the next environment. DevOps tools like Octopus deploy can do that.

[mdenn]

Yeah, a lot of the Power Platform doesn't seem too mature, in my opinion.  For example, the only way to use source control seems like a manual process of exporting unmanaged .zip files or running a bunch of pac CLI operations.

[Karintie]

I get a similar issue and as the solution is Managed, you also cannot update the environment Variable afterwards.