Migrate 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,
@Pstork1 @Expiscornovus @ManishSolanki @RezaDorrani

Categories:

Building flows

I have the same question (1)

All responses (12)

Answers (1)

Verified answer

Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

1) When moving to a production environment you should export the solution as a managed solution. This will make it more difficult for someone to change the apps and flows once its imported into production. Any changes should be made back in the development environment and an new managed solution imported with those changes to production.

2) Before you export the solution make sure you remove the current and default values from the environment variables. Then make sure you Publish all Customizations during the export. During Import you will be prompted to set the new current values for the environment variables. You will only be prompted if you remove both the current and default values. With a managed package you won't be able to change them after the import.

Here's the official documentation from MS on using solutions. Solutions in Power Apps - Power Apps | Microsoft Learn

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report

Thank you @Pstork1
According your second point. 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
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

No, you have to create them in the default solution. But if you remove both the current value and default value from them before export then you will be prompted to update the values during import. But that prompt only happens if the environment variables exist in the solution and have null values.

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report

ok , got it now 🙂
And if I want to make further changes in my Default environment, shall I :
1- add the old values for the environment variables in Default environment,
2- Make changes
3- test
4- remove both the current value and default value from the environment variables,
5- export solution
6- Import in the Production environment and update the variables during import to Production

Is it correct?

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

Just one additional step. Make sure you publish all customizations between #4 and #5. Otherwise the exported solution won't reflect what you did in #4.

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report

Thanks @Pstork1 .
Now Im getting permission error while trying to publish all customizations between #4 and #5. So I assume I need to ask for furthure permissions to pass ths step 🙂

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

Check with your administrators. System Customizer is normally the role for developers making flows and apps. But if you are using any Dataverse tables that may require extra permissions too.

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report

No Im not using Dataverse, My source is SharePoint

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

Then check to make sure you are system customizer role in the environment. That should give you the permissions you need.

Was this reply helpful? Yes No
Mana 171 on at

Like (0)

Report

It seems like the It department is not gonna give the System customizer role so I have to ask them everytime I want to move to publish. What will happend if I dont use the 'Publish all Customizations'. will I miss my changes?

Was this reply helpful? Yes No