Working with Power Automate Solutions: Exporting An Unmanaged Solution

Power AutomateThis article is part of the Working with Power Automate Solutions series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

If you are developing a Power Automate solution and want to either move it to a new development environment or add it to a source control system, you can do this by exporting the solution as an unmanaged solution. Do this be navigating to the Solutions page, selecting the solution you want to export and click the Export solution button near the top of the page (ringed in red):

Solutions page with a solution selected and the button ringed

If you haven’t published your solution, you can do this on the Before you export pane which opened at the side of the screen; click the Publish button:

Before you export pane showing the Publish button

Publication may take a few minutes, but once it is finished, a confirmation will be displayed and you can click Next to proceed:

Before you export pane showing publication complete

Change the version number if required; as I am exporting to add to source control, I am happy for the final segment to increment as it fits my version numbering pattern.

As I want a solution for source control, this means I need an unmanaged solution; under the Export as title, click the Unmanaged radio button.

Click Next to begin the export:

Export this solution pane showing version numbers and types of solutions which can be exported

The export solution pane will disappear, but a new grey bar at the top will be displayed, confirming that the export is being prepared:

Solutions page showing export is currently processing

Once the solution is ready, the grey bar will be replaced by one confirming export has been successful:

Solutions page showing export was successful

You will then see the standard download prompt in your browser of choice; click Save (or equivalent):

Browser download confirmation dialog

You will now have a zip file containing the solution for you to either add to your source control system or import into another development environment; you should not, as best practice, import the unmanaged solution into any other type of environment, including QA or UAT and especially not a production environment.

Working with Power Automate

Working with Power Automate
What is Power Automate?
What Type of Flow Are Available?
What Type of Cloud Flows Are Available?
Power Automate with Business Central
Working with Power Automate Solutions: What Are Solutions?
Working with Power Automate Solutions: What Types of Solution Are There?
Working with Power Automate Solutions: What is a Solution Publisher?
Working with Power Automate Solutions: Create a Solution Publisher
Working with Power Automate Solutions: Create a Solution
Working with Power Automate Solutions: Publish a Solution
Working with Power Automate Solutions: Version Numbering for Solutions
Working with Power Automate Solutions: Exporting An Unmanaged Solution
Working with Power Automate Solutions: Importing An Unmanaged Solution
Working with Power Automate Solutions: Exporting A Managed Solution
Working with Power Automate Solutions: Importing A Managed Solution
Working with Power Automate Solutions: Change the Managed Properties of a Solution Component
Create a Visio Diagram of a Flow
What Are Environment Variables and Why Should They be Used?
Create an Environment Variable
Create a New Cloud Flow From a Template
Managing Large Flows
What is a Scope?
Example of How to Use a Scope
Best Practice For Using Scopes
Working with Power Automate Child Flows: What are Child Flows?
Working with Power Automate Child Flows: Create a Child Flow
Working with Power Automate Child Flows: Change Run Only Users For Child Flow
Working with Power Automate Child Flows: Add a Child Flow To a Parent Flow
Working with Power Automate Child Flows: Test the Parent/Child Flow Examples
Working with Power Automate Child Flows: Error Encountered Saving a Flow Which Calls a Child Flow
Working with Power Automate Child Flows: Error Encountered With Surprise Extra Parameters for a Child Flow

What should we write about next?

If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.

Your Name

Your Email

Suggested Topic

Suggestion Details

1 thought on “Working with Power Automate Solutions: Exporting An Unmanaged Solution

Leave a Reply

Your email address will not be published. Required fields are marked *