Open mathiasbl opened 4 years ago
The core underlying problem here is that the connections within the Power Automate/Flow don't update when the solution is imported. As a result, the imported Power Automate has to be edited before it can be turned on. In a new environment, this also requires creation of new connectors and the associated security related to them, so this is not a simple thing to automate. If you use to other CDS connector that only connects to the Current Environment, the Import will address this, but this still doesn't address connections to other apps.
@mathiasbl @mattp65
Seems to me this is a bit more involved. Do you use the package deployer or have any custom code running in the pipeline?
When you (re)import a solution which contains solution aware flows, these flow get turned off and you have to manually enable them. Would be nice to have a task which automates this.
Of course when you first import the new flow into a new environment you have to fix the connections but after this I don't see a reason why these flows are turned off.
What do you think? Example here on how to turn on a flow