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?
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
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
45 | |
16 | |
15 | |
14 | |
13 |
User | Count |
---|---|
78 | |
38 | |
27 | |
21 | |
18 |