All Content
Timespan
explore our new search
Step-by-Step Guide: Cloning Power Automate Flow in Solution
Image Source: Shutterstock.com
Power Automate
Oct 20, 2022 6:10 AM

Step-by-Step Guide: Cloning Power Automate Flow in Solution

by HubSite 365 about Christian Badouin (hubsite365.com)

Citizen DeveloperPower AutomatePower Automate

Master the art of cloning Power Automate Flows within a Solution with our detailed Microsoft expert guide.

The blog post composed by Christian Badouin from hubsite365.com illustrates the process of cloning a Power Automate Flow within a Solution. Those who use Power Platform will find this method to be a professional means of Application Lifecycle Management (ALM), including for Flows. However, the existing interface only permits a "Save As" function and currently lacks an option to add Flows back to an existing Solution. Christian presents the procedure of copying Power Automate Flows within Solutions.

For uncomplicated Flows, utilizing the Preview Feature Copy/Paste is the simplest workaround. However, this solution is not effective for more intricate Flows. Fortunately, there is a neat workaround courtesy of Postman. This workaround method is aptly demonstrated in the blog, complete with useful screenshots.

The first step involves creating a Clone Destination Flow within the existing solution. This new Flow serves as the target for the cloning or copying operation. It doesn't matter what data it holds initially, because it will be overwritten by a Postman call eventually.

Step two requires the user to save the Clone Destination Flow while simultaneously determining the URI and Bearer Token. This can be achieved using the developer tools (F12) and saving the Destination Flow. It is also important to remember to remove any accidental white spaces or line breaks!

In the third step, the source Flow gets saved in order to determine the Request Body. Similar to the Destination Flow, the source Flow needs to get saved while developer tools are open.

In the final step, a new request gets made in Postman. The Authorization needs to be set to "Bearer Token" and the previously stored value of the Bearer Token needs to be added. After adding the necessary details (Request URL of the Clone Flow, Body Format set to RAW, Format set to JSON, Request Body of the source Flow, and replaced Displayname), the Request can be sent in Postman. If successful, a status 200 is returned, and the result can be seen in the Clone Flow.

The blog concludes that this workaround saves significant time. Once users have familiarized themselves with the principle, copying or cloning Flows should be efficient.

General Thoughts About Power Automate

More broadly, Power Automate, also known as Microsoft Flow, is a versatile tool with manifold uses. It allows for streamlined business operations by enabling automated workflows between your favorite applications and services. The platform helps in the synchronization of files, getting notifications, data collection, and much more. Notably, Power Automate offers a vast selection of templates, making it easy for users to get started on standard tasks. This efficient tool ensures smoother, less time-consuming operations within your business and allows your workforce to focus on more pressing matters.

Find more on Power Automate.

Read the full article Clone a Power Automate Flow within a Solution

Power Automate - Step-by-Step Guide: Cloning Power Automate Flow in Solution

Learn about Clone a Power Automate Flow within a Solution

The current text delves into the intricacies of duplicating or cloning a Power Automate Flow within a solution. Combating the industry’s problem of not being able to re-add Flows to an existing solution despite being able to 'Save As’, the current article provides solutions to complex Flow problems.

With the typical interface enabling simpler Flows to bypass the issue through its Preview Feature Copy/Paste command for Actions, those requiring a more complex operation don’t fare as well. Thankfully, a workaround course exists via the developer tool, Postman.

Following a tiered process, firstly, a new Flow is created within the existing solution. This action creates what's known as a Clone Destination Flow. This Flow is essentially the clone's target. Ultimately, this is wiped once a Postman Call is established.

  • Create a Clone Destination Flow
  • Save Clone Destination Flows to ascertain URI (Uniform Resource Identifier) and Bearer Token requirements for Postman Calls
  • Save Source Flows to fix the Request Body requirement
  • Craft Postman Request using the above components

Therefore, the URI and the Bearer Token information for the Postman Calls are captured by saving the Destination Flow. Here, developer Tools F12 is put into use and the Destination Flow saved. There may be multiple requests traced. Therefore, it's crucial to inspect which request instigates the PATCH.

Beware of inadvertently copied spaces and line breaks. Attention must also be paid to the Request Body. This is also accessible by opening the developer Tool F12 and storing the Source Flow.

Having collated all the necessary data points, one can then proceed to the next step–to put together the Postman Requests. It's crucial to set the Authorization to "Bearer Token" and paste the previously stored Bearer Token value.

Some additional details, such as the Request URL of the Clone Flows, setting Bodyformat to RAW, selecting JSON format, adding Source Flow's Request Body and replacing the Displayname have to be filled in as well.

After filing all the requisite information, the Send button in Postman is clicked to send the Request. In a successful execution, one should receive a Status 200 return and then, the clone Flow becomes operational.

Essentially, several aspects such as saving time and swiftly copying or cloning Power Platform Flows are some of the key benefits once the process is mastered. Though initially, it may seem demanding, it could augment the efficiency of the Flow process remarkably. This course should thereby offer valuable guidance to Citizen Developers aiming to master the cloning process.

More links on about Clone a Power Automate Flow within a Solution

Copy/Duplicate a Flow in a Solution
Mar 3, 2020 — Yes you can but only way is to edit the xml files. Follows the below steps: Note: Before you do this take a backup copy of your existing solution. 1. Export the ...
Duplicate / copy a flow within a Solution - Power Automate Ideas
Solutions are the only way to use the "Child Flow" feature (e.g. subroutine) for repetitive tasks. Being able to duplicate flows within a solution will allow us ...

Keywords

Clone Power Automate Flow, Automate Flow Solution, Duplicate Power Automate Flow, Clone Automate Flow, Power Automate Solution, Automate Flow Copy, Replicate Power Automate Flow, Power Automate Cloning, Power Automate Flow Duplication, Solution Automate Flow Clone