• Yash Agarwal

Working with Power Automate Flows in Solutions V2

In this #PowerShot, I will show you how to resolve issues that occur when you move a flow out of a solution and try importing it as an independent flow into a different environment or tenant.

Let's Get Started

We will take a look at the steps that can be followed to import a flow created in a solution as a regular flow to a different environment or tenant and resolve any issues that arise in the process.

Flow config

Below is what the details page looks like when you open a flow from a solution in edit mode. It expects the connection references on the top right instead of connections for flows created outside of solutions.

Error Message

Below is a screenshot of a sample error message that displays and note that this flow does not show any connections as the generic ones (flows created outside solutions when imported independently) and expects the connection references to exist.

The request failed with error: '{"error":{"code":"PackageFlowMissingConnectionMap","message":"Flow resource 'guid-7a2c-464c-b9e0-6370a55a0915' missing mapping for connections 'shared_commondataserviceforapps,shared_office365,shared_sharepointonline'."}}'. The tracking Id is 'd2973d33-a19a-4571-90d9-guid'.


Open the flow from the solution in edit mode and click on save as and save the flow as a new flow. Once you do that, you will be asked to authenticate to the services being used in the flow to continue. Provide those connections and then provide a name for the copy flow and save it.

Once the flow is saved, (it is saved in a disabled or turned off state) you will see the connections instead of connection references as shown in the image below.

Now once the flow is save as a regular flow outside solutions, when you try exporting it, you will see the screen below instead the previous one where the Related Resources was blank for the connections.

After exporting the flow and then importing it to the other environment or tenant, you may see that despite providing all the connections, the flow may still fail to import. Now depending on the issue (for example mapping the SharePoint sites or lists on an action), you can hit the save as new flow button as shown in the below image.

Once you click the Save as new flow button, the flow will open in edit mode in the new environment or tenant and then you can make appropriate changes and then save the flow successfully.

In this post, we saw how to debug and resolve error when flows created in solutions are independently moved to a different environment or a tenant outside the solution. Connection references are an important factor to weigh in and for flows that are moved to solutions or are created as a part of a solution, this is a required property and causes errors if the flow needs to be separately imported elsewhere.

I hope you found this interesting and it helped you. Thank you for reading.

Recent Posts

See All