cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Best practice for updating "production" flows?

I currently have a flow that is shared with a small group of users and intended to be pushed to the entire organization soon. I want to make changes to this flow without risking it being broken or requiring that users add another flow button to their mobile app. I want the update to be transparent to users.

 

What I'm planning to do is export the production flow and reimport it with the title "test_..." and make changes there. Once I have a new version to push I'll export the test flow, and reimport it under the production title. Are there any foreseeable problems with this method?

1 REPLY 1
v-yamao-msft
Community Support
Community Support

Hi @Anonymous,

 

As long as you follow the steps that suggested in this doc, I assume that the flow could be exported and imported without issues. However, there are some know limitations, such as the ability to export/import custom connectors, and the ability to re-configure the data sources for the app during import, etc.

More details about the steps and limitations, please check the doc at here:

https://flow.microsoft.com/en-us/blog/import-export-bap-packages/

 

Best regards,

Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Users online (3,012)