cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Helper I
Helper I

How to Move Flows Across Environments while keeping 'on'

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

 

 

5 REPLIES 5
Super User II
Super User II

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

@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?

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

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)

 

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

 

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

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Microsoft Ignite

Microsoft Power Platform: 2021 Release Wave 1 Plan

Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (49,214)