About the delivery
ProsessPilotene delivered Deployment Settings for E.A. Smith AS (2024).
All environment variables after project restart
Value creation
Avoids combining manual and automatic deployment for flows --> one way of doing things.
Time saved and increased control over environment variables
The solutions
- Deployment Settings
Deployment Settings: Microsoft documentation: Pre-populate connection references and environment variables for automated deployments using Power Platform Build Tools - Power Platform | Microsoft Learn
Case 1: In a new project, you create a new Power Automate flow in the development environment. The flow is triggered by and processes data in Dataverse in its own environment. This flow is part of a solution that is exported from the development environment and must be imported manually into another environment. A dialog box then appears, asking the user to map the connection used in the development environment to a connection to be used in the environment into which the solution is imported.
If this import had been performed using a pipeline, the import would not have been completed, and the flow would have remained incomplete and not ready for use.
Case 2: The customer has a line-of-business system with different URLs for dev, test, and prod. It is preferable not to hard-code these URLs. Environment variables are therefore used. An environment variable is created in dev, and a value is set for the current environment. After importing the solution into test and prod, the values must be set manually in these environments and must not be changed.
Deployment Settings makes it possible to perform the mapping using a settings file (.json), where the mapping is defined as text and handled during solution import. There will be one settings file per import environment.
For environment variables, a name will be specified for use across solutions, along with a value to be used in the current environment.
The same will be done for connection references (Connection References)
Example from Microsoft: (a connectionId for a Connection Reference might typically be as follows: "shared-commondataser-e8db1c1a-31fc-4006-98e0-0f3c58eb9667")
Area and keywords
Other
Deploy,Solution import,Import,Pipeline,Environment variable,Connection Reference,Connection references