migrating solution containing Power Automate and PowerApps

(0) Share

Report

Posted on by Mana

171

Hello Community,

I'm currently seeking your expertise regarding a migration scenario involving a solution that utilizes multiple data sources. Here's a brief overview:

I have developed a solution in the default environment, consisting of one PowerApp and 19 Power Automate flows. The solution interacts with two different SharePoint sources: "Site_Default" and three SharePoint lists named "List_1," "List_2," and "List_3." To ensure flexibility, I have implemented environment variables for these data sources.

Now, I am planning to move this solution to a Production environment. In the Production environment, I have set up a SharePoint site called "Site_Prod" with three SharePoint lists having the same names and column structures as in the default environment.

I have a few questions regarding the migration process:

Should I move the solution as a Managed or Unmanaged package to the Production environment?
- What are the considerations and best practices for choosing between Managed and Unmanaged packages in this scenario?
How can I ensure that the Power Automate flows in the solution are updated to point to the new data sources in the Production environment?
- When and where should I modify the flow configurations to switch from the default environment's data sources to the Production environment's data sources?
- Are there any potential challenges or pitfalls I should be aware of while updating the flow configurations?

I appreciate any insights, tips, or recommendations you can provide to help me navigate this migration process effectively. Thank you in advance for your assistance.

Best regards,
@WarrenBelz

Categories:

Governance & administering

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @Poma1,

You should use a Managed Solution to import to your downstream test/uat/production environments. Unmanaged is meant for development where you make changes to customizations. You typically don't want to allow unmanaged customizations directly in production because you can have inconsistencies between environments, making troubleshooting issues difficult.

Using SharePoint data source environment variables for your lists is the correct approach here. Your flows should use environment variables in your SharePoint actions instead of specifying the site/list directly in the action. That way you don't have to reconfigure your Flows everytime you import to a new environment.

Before you export your solution, make sure the environment variable value is cleared out. When you import your solution to a new environment, the import wizard will allow you to enter the environment value with the appropriate SharePoint site and list you want to use.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report
Copy link

Link copied!

I alredy point to the Evironment variables in my Power automate flows instead of point directly to sharepoint sources. But do you mean its better not to create any environment variables in my default solution and do it during importing the solution to Production?

Was this reply helpful? Yes No