How to Move Flows Across Environments while keeping 'on'

(0) Share

Report

Posted on by jzia93

Hi,

I have built several flows in a solution in my Development Environment.

When moving from Dev to Test manually (downloading solution file and importing using Solution UI) the flows are able to be moved in an active state.

When using Azure DevOps to automate the migration, the flows are migrated successfully but are in an 'off state'

I am only using the Common Data Service (Current Environment) connector.

Would appreciate any ideas as to how to keep the flows 'On' During import

Categories:

General topics

All responses (5)

Answers (0)

Sort by

manuelstgomes 6,643 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @jzia93

You can use Power Automate to enable other Power Automates.

https://docs.microsoft.com/en-us/connectors/flowmanagement/

I think this will solve your issue.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel
jzia93 40 on at

Like
a
(0)

Report
Copy link

Link copied!

@manuelstgomes

Thanks, hadn't seen that connector. Had some trouble getting it to work initially but seems to do the job.

My only question - why are the flows not turned on by default? Is there some way to enable this behaviour?
manuelstgomes 6,643 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @jzia93

I think this is the way of Microsoft protecting you from starting to parse data if you're not ready.

In this way you're forced to enable it making you aware that is working.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel
jzia93 40 on at

Like
a
(0)

Report
Copy link

Link copied!

I don't believe so - if you are using the Common Data Service (Current) Connector and importing the solution using the Power Apps UI the flows are imported in the same state as they were exported.

i.e. If I export manually with flows set to 'ON' the flows are imported in an 'ON' state.

The behaviour I mentioned only applies when using Azure DevOps (haven't tried to do it in PowerShell)
jzia93 40 on at

Like
a
(0)

Report
Copy link

Link copied!
@manuelstgomes, removing this as a solution so people don't get confused. Following reasons:

The Power Automate Management Connector is not suitable for working with Solution-aware flows
All flows deployed with DevOps will need to be Solution Aware