Power Platform Community Forum Thread Details

Because I don't want to have anything related to the development environment (or any environment for that matter) in the repository source code, I must take extra steps sanitize the solution environment variable values with CI/CD pipelines. Anyone have some experience with this or best practice suggestions?

I find it somewhat confusing having to clear environment variable values in a solution before exporting a solution in the first place, doesn't this make the optional default value redundant? If nothing is already set in the target environment upon import, then a default value is used instead, I believe this is usually how environment variables tend to work in traditional software development.

Can we call them environment variables when the values are included in an export from an environment? One thing that is perhaps related to the term "environment", is that their values are available to other solutions within the environment. Perhaps it's because "environment" refers to environment as a concept rather a specific environment, in any case, I'm confused 😄

Categories:

Microsoft Dataverse with Power Apps