I need a hint on how to introduce changes to my flow using best practices. I developed some flows and shared them in the organization, but some new ideas came up and I would like to update the flow with minimal downtime. The change is not a quick fix like a typo that can be changed instantly, but rather requires some testing after the change and some back and forth changes during the testing.
What is the approach in Power Automate? Should I create a copy of my flow and edit it?
Furthermore: is there a way to test Power Automate flow without interacting with users involved in the flow? I have an approval step that requires two users to approve. Can I test it in detail specifying that one user approved and the other did not or I can just mark a step as failed and see how it is handled?
You should create a Solution. Add or Create your Flows directly in the Solution.
Then you can export the solution (when you are done) as a managed Solution, and then Import it into Prod and it will update and you will have minimal impact.
As for your second question.
The best way is to make sure that the people being added to the approval are NOT hard coded.
for instance
Let's pretend its 1-M people.
Put those people in a semicolon concatted String/Text Environment Variable.
Then in your Dev environment just add yourself, or you and another dev/test to validate multiple people.
once you move your solution to another system, on the Import of that solution, it will allow you to modify the value to be the real people. THis way you can test it with whomever you want in whatever environments and then in Prod, add the real people.
This is the proper way to do what you asked on both accounts.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
4
Share
Report
All responses (
Answers (
