Flows that use other solution components
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Power Platform product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | Early access | General availability |
|---|---|---|---|
| Admins, makers, or analysts, automatically |  Nov 2, 2019 |
- | - |
Feature details
The Microsoft Power Platform is continuing to adopt a single packaging mechanism. We're continuing to close gaps so that any solution component has consistent behavior and pre-existing user workflows aren't negatively affected. Combined with enhancements to our developer tooling, you can manage all customization in source control, enabling continuous integration and continuous delivery with fully automated build and release pipelines.
With this release, there are three important updates:
- Flows can now leverage Environment Variables. Environment variables allow you to transport application configuration data with solutions and optionally manipulate the values in your Application Lifecycle Management (ALM) pipeline. They act as configurable input parameters allowing you to reference an environment variable within other solution components. You can update a value without modifying other components directly when using environment variables.
- You can add Custom connectors to solutions. This means if you have additional custom endpoints that you want to connect you, you can store that definition alongside your flows in a solution, and when you export and import your solutions to a different environment the connector definitions will be transported as well.
- Dependencies are tracked and enforced for new solution components. For example, if a flow uses an entity in the Common Data Service, that will now be known at solution export and import time.
See also
Feature exploration (video)
Power Automate blog (blog)