cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bhitchlockfcs
Resolver II
Resolver II

Copy/Duplicate a Flow in a Solution

I have a Flow in an existing solution for which I need to create several variants. Ideally I would copy the flow and edit the copy. 

Unfortunately the copies are created outside the solution and are not visible to import into the solution.

Any ideas on how to replicate a Flow inside of a Solution?

 

Thanks,

 

Brian

2 ACCEPTED SOLUTIONS

Accepted Solutions
abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

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 current solution

2. Once the solution is exported then unzip the current solution

3. You will see the following files and directory

     image.png

 

4. Go to Workflows directory. Here you can see the flow json file.

 

5. Duplicate the flow file and rename to another filename and new GUID. To generate new GUID use this site https://www.guidgenerator.com/online-guid-generator.aspx

 

6. Once the file is copied and renamed with new GUID you will have two json flow files like below. Makes sure GUID must be capital case.

 

image.png

7. Next go to back to parent folder and open customizations.xml file

 

8. Copy and paste (duplicate) the workflow element. See below. Here the highlighted part is the first flow you created. Below you can see my new workflow node I copied.  change the GUID's workflowID (Use the GUID you generated), Name and JsonFilename. Please be careful that all are case sensitive. So follow the same pattern as the first workflow where you copied form.

 

image.png

Save the file.

 

9. Next open the Solution.xml file

Duplicate the Root Component. Again the id is case sensitive. Use the same flow GUID as above.

 

image.png

 

   Save the file

 

10. Finally Zip all the files.

 

12. Delete your existing solution. (Please take a backup copy of your solution).

13. Import the new zip solution.

 

Here is my result

image.png

If you need any help in this please let me know.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

View solution in original post

Welbywelb
Advocate III
Advocate III

Sorry I know this is old but it might help someone.

Actually you can do it with Postman. Create a Skeleton destination flow (just through away steps in it) and save it.

In Chrome open the inspect window and navigate to the "network" tab and capture the PATCH post URL (we will use this in Postman) and Bearer token.

Go to the flow you want to copy and in Chrome open the inspect window and navigate to the "network" tab. Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..). 

Got to Postman and create a new Patch request (copying your Bearer token to the authentication) and past the body of the flow you want to copy. Lastly edit the "displayName" so it matches what you called the Skeleton flow.

Hit Post and the Flow should be be updated with the contents of the one you just copied.

 

Really ugly way of doing but its probably quicker than exporting the entire solution and updating it.

 

You might need to watch out for the only "16 connection limit" on one reference issue - if you get this open the Skeleton app and connect to CDS and create a new connection save it as before and examine the properties payload you will see the mentioned connection has changed name - copy this to the same field in the payload you want to test and you should be up and running. 

View solution in original post

39 REPLIES 39
abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

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 current solution

2. Once the solution is exported then unzip the current solution

3. You will see the following files and directory

     image.png

 

4. Go to Workflows directory. Here you can see the flow json file.

 

5. Duplicate the flow file and rename to another filename and new GUID. To generate new GUID use this site https://www.guidgenerator.com/online-guid-generator.aspx

 

6. Once the file is copied and renamed with new GUID you will have two json flow files like below. Makes sure GUID must be capital case.

 

image.png

7. Next go to back to parent folder and open customizations.xml file

 

8. Copy and paste (duplicate) the workflow element. See below. Here the highlighted part is the first flow you created. Below you can see my new workflow node I copied.  change the GUID's workflowID (Use the GUID you generated), Name and JsonFilename. Please be careful that all are case sensitive. So follow the same pattern as the first workflow where you copied form.

 

image.png

Save the file.

 

9. Next open the Solution.xml file

Duplicate the Root Component. Again the id is case sensitive. Use the same flow GUID as above.

 

image.png

 

   Save the file

 

10. Finally Zip all the files.

 

12. Delete your existing solution. (Please take a backup copy of your solution).

13. Import the new zip solution.

 

Here is my result

image.png

If you need any help in this please let me know.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Jcook
Most Valuable Professional
Most Valuable Professional

@abm that is a great post.. definitely saving this for later.

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





abm
Most Valuable Professional
Most Valuable Professional

Hi @Jcook 

 

Thanks for the comment. Really appreciated it. Keep up the good work. I can see you doing well in this community sharing your knowledge.

 

 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Jcook
Most Valuable Professional
Most Valuable Professional

@abm thanks, I enjoy helping where I can. Also I have found that I learn so much more when helping others.

So it’s a win win.

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Thanks @abm,

 

I was afraid that would be the answer. These Flows are part of a larger Model Driven App solution. So editing and replacing the solution is a little more involved. Does the content of the solution or whether it is managed/unmanaged make a difference to your workaround?

Thank you for the detailed directions.

 

Brian

abm
Most Valuable Professional
Most Valuable Professional

Hi @bhitchlockfcs 

 

I haven't checked the managed solution to extract and reconstruct the solution. It may be possible. Not sure that is supported or not?

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
FIN
New Member

@bhitchlockfcs 

Also you can go to your flow click save as (a new copy will appear in "My flows") and add new flow to your solution.

 


@FIN wrote:

@bhitchlockfcs 

Also you can go to your flow click save as (a new copy will appear in "My flows") and add new flow to your solution.

 

You would think it would be this easy.  It would save a lot of time for larger projects.  The copies are not available to me either when attempting to add them to my solution.


 

Now I see why I had this problem. So there is a list of known limitations (for example Button triggered flows are not available in solutions). So if you want to copy and import a flow you'll need to switch trigger (or anything else on the list) to be able to import it.

See:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solutions-overview#known-limita...

 

So i created a solution and 2 flows:

FIN_1-1606929725271.png

Saved the copy:

FIN_2-1606929780826.png

 

And on add existing flows I see only Copy of - TestSaveAs - OneDrive

FIN_3-1606929841547.png

And i can add it.

 

So to be able to import existing flow you'll need to change/delete some steps.

dialedin
Advocate II
Advocate II

Ah, good find.

 

In my case, I created the copy from a flow already in the Solution, so it didn't have any unsupported limitiations.

Welbywelb
Advocate III
Advocate III

Sorry I know this is old but it might help someone.

Actually you can do it with Postman. Create a Skeleton destination flow (just through away steps in it) and save it.

In Chrome open the inspect window and navigate to the "network" tab and capture the PATCH post URL (we will use this in Postman) and Bearer token.

Go to the flow you want to copy and in Chrome open the inspect window and navigate to the "network" tab. Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..). 

Got to Postman and create a new Patch request (copying your Bearer token to the authentication) and past the body of the flow you want to copy. Lastly edit the "displayName" so it matches what you called the Skeleton flow.

Hit Post and the Flow should be be updated with the contents of the one you just copied.

 

Really ugly way of doing but its probably quicker than exporting the entire solution and updating it.

 

You might need to watch out for the only "16 connection limit" on one reference issue - if you get this open the Skeleton app and connect to CDS and create a new connection save it as before and examine the properties payload you will see the mentioned connection has changed name - copy this to the same field in the payload you want to test and you should be up and running. 

Wow, this s/b the actual solution. Well done.

Jcook
Most Valuable Professional
Most Valuable Professional

Awesome post @Welbywelb !


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Thanks Welbywelb!

 

Your solution worked great!  Where you stated, "Click the "Save" on it and capture the body of the Patch command (Request Payload - starts "properties:..).", when I saved the file from Chrome Dev Tools, the double quotes were escaped by backslashes, that I had to remove (a simple find and replace).

 

In file saved from Chrome:   

"text""{\"properties\":{\"definition\":{\"$schema\":...
 
In postman, placed in the Body - Raw section,  I put:
{"properties":{"definition":{"$schema":...

thx @Welbywelb for the fantastic workaround. I've added some more details including screenshots 🙂 The post is in german but this should be no problem. Klonen bzw. Kopieren von Power Automate Flows innerhalb von Solutions | applied technologies GmbH

Your article explains @Welbywelb solution in details! Precious! Thank you both!

GamerTuku
Advocate I
Advocate I

   

maxpower45255
Advocate III
Advocate III

The solution I found without exporting/reimporting the solution is to use "save-as" for the flow you're interested in. Then importing the new exported flow back into the solution. I'm always weary of deleting my solution and trying to reimport especially if it's a critical flow. I have seen odd issues over time and don't trust the solution import too much.

Has anyone tried this workaround and what has been your experience? 

 

I really wish Microsoft would fix the "Save-As" and the "Clone" features so we can safely work/test our work. The "save-as" should just save the flow inside your solution if the flow is already inside, and not outside. 

The "Clone" solution should clone the entire solution including flows and connection references (I read this article and made me scared to even try that feature: Solved: Clone Solution issue - Power Platform Community (microsoft.com) See also this for more info: Power Platform – Clone Solution | innovativeaj (wordpress.com)

Maybe MSFT will fix this in future releases. Hope MSFT is reading this blog 🙂 

 

Welbywelb
Advocate III
Advocate III

Hi Maxpower4522,

 

Very interested in this so I just tried to do a "save as" from within flow in a solution and the flow is placed in "My flows".  If I try to "Add existing" ..."Cloud flow"-> "From Dataverse or Outside Dataverser" then the flow is not visible (I've assumed this is what you mean when you say "importing the new exported flow back into the solution") but perhaps there is another way to do it from inside a solution. FYI this was a "manually triggered flow" so this might be the issue.

 

Can you share the navigation steps you do which successfully imported a previously "save as"'d flow please if different from above?

Also what kind of flow trigger is used with within it?

 

FYI it appears that there are many reason for this not to work see - https://docs.microsoft.com/en-gb/powerapps/maker/data-platform/solutions-overview#known-limitations

 

This is the reason I provided my solution above which basically allows you cut and paste the code content for a any flow into a skeleton flow which you have created where you want it (inside a solution or not).

I totally agree that we shouldn't have to do this but until MS gets the finger out its the best solution I've found to date.

 

Thanks.

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,240)