cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
srinathgadalaye
Regular Visitor

PowerApps Import Solution doesn't Turn ON Flows

Hi,

 

I am Exporting and Importing solutions from one env to another env using Power Platform Tasks of Azure DevOps.

 

My Import got successful, but after importing I can the solutions in make.powerapps.com under CloudFlow option, my Solution Names Status are not Turn ON?

 

Can anybody tell me, which option should I select in Power Platform tasks of Azure DevOps to Turn them ON automatically.

 

6 REPLIES 6
v-jefferni
Community Support
Community Support

Hi @srinathgadalaye ,

 

I'm afraid you will need to turn on the flow anytime you export and import a solution which includes the flow.

 

If you still could not see the flow in Power Apps, refer to below thread, and you could try the whole process:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Flow-goes-lost-while-export-importing-a-solu...

 

  1. Export the app,entities and the flow as a managed solution
  2. Import it into our test environment.
  3. Open the flow in edit mode and re-assign the connections
  4. Turn the flow on
  5. Save the flow
  6. Open the app and go to the flow trigger
  7. Select triggering control -> property where trigger will be called in -> Action -> Power Automate
  8. This will list out the flows available in the solution
  9. Make a copy of the trigger from the formula bar (to retain the parameters and the return data)
  10. Add the flow from the list and paste in the parameters and the formula that captures the return data
  11. Save and Publish.

Hope this helps.

 

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

MJKirts
Frequent Visitor

@v-jefferni Can you elaborate on why it is that imported flows are turned off by default and must be turned on manually?  Is this a bug or is there a logical reason for this?  If a bug, is it going to be fixed any time soon?  If this is normal behaviour, is there an automated way to turn flows on (e.g. using Power Platform Build Tools) Thanks.

Hi @MJKirts ,

 

It's by design and the reason I guess could be to avoid automated flows to lead to unexpected consequences. After double checking the imported flows you can turn them on and get them to work properly.

 

Hope this helps.

 

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Thanks.  That is helpful.  Is there anyway to turn the flows on programmatically (via Powershell script, Azure DevOps pipeline, etc)? or must it be done manually via the make.powerapps.com portal?  

Hi,

Did you ever find a way to turn on these flows programatically (hopefully through powershell cmdlet or Power management actions in other flows).

Unfortunately not, but haven't looked into it for over a year.  Things may have changed.

Helpful resources

Announcements
Power Apps News & Annoucements carousel

Power Apps News & Announcements

Keep up to date with current events and community announcements in the Power Apps community.

Power Apps Community Blog Carousel

Power Apps Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Top Kudoed Authors
Users online (4,486)