Power Apps: Move apps & flows to new environments without breaking! Managed vs Unmanaged solutions

[@AmazingApplications]

Your got me at the thumbnail. The graphics really helped illustrate the solution deployment concepts. Your channel is becoming a great resource for Power Platform professionals.

[@Untethered365]

Thank you! I can't wait until copilot can generate animations.

[@francomussocom]

Excellent explanation. The visuals and guided example really help make it real rather than the usual reams of text / theory

[@SeanAstro]

The visuals took forever but I couldn't find another way to explain it.

[@francomussocom]

@@SeanAstro I’d say well worth the effort 👌

[@ptr_mic]

Professional video. Thanks for sharing. I really like the format and how the information is presented.

[@SeanAstro]

Thank you! It was the only I could think to make it so it made sense

[@dogzrgood]

Such a good video. very clear.

[@RajM-g7b]

Very well explained!! I started developing model-driven apps and would pull my hair every time I had to deal with exporting a managed solution to production. Your illustrations clearly help break down the complex concepts.

[@Untethered365]

Awesome! I'm so glad it helped. I was trying to help make it visually easy cause it is tricky :)

[@Tiago22049316]

Your videos are very useful and the way you explain it makes all the difference, congratulations on the work and I hope you continue publishing more videos Thanks!

[@SeanAstro]

Absolutely thanks Tiago!

[@DonCurrier]

How do I manage my environment variables when going from dev to prod? Before exporting, I turn export value to no. Then when importing, I expected to provide a new URL for my sharepoint site and pick from the list displayed. I am not seeing the production environment in the dropdown to change the sharepoint site. UPDATE: I realized that the dropdown to select an environment is a cache of recently used. But since I code in one main account, and build the sharepoint site with my own account, the production site wasn't displaying in the dropdown. so, I opened the prod site with the account i was creating the app with, copied a file to the document's library, then deleted said document. restarted the import process and low and behold, the prod site was now listed in the dropdown to pick the new sharepoint site.

[@Untethered365]

See my other video on Canvas App deployments. This is for Dataverse.

[@mehuljain-s4y]

That was a really helpful video. I have got one question - in the prod when we remove the unmanaged layer to push through the changes made via managed one then what happens to the - customisation and data of the unmanaged layer ? Thank you

[@SeanAstro]

Customization will be gone and data being gone depends on what kind of customization it was.

[@Kylbigel]

All signal, zero noise.

[@swaminawale7386]

Good explanation 😃 How abd what is the best approach for cross tenants migration of flows and apps?

[@Untethered365]

I've got a video on best practices in deployments coming soon!

[@mardithpascua8112]

Hi, just a few question: If the objects stays in the environment if you delete unmanaged solution (example: solution1 version 1.0.0.10). Then for example, you have a copy of solution1 version 1.0.0.5, THEN, imported it to the same environment and it contains Send Email Flow with 3 actions but the current Send Email Flow in the environment contains 5 actions, does it overwrite the existing flow and make it 3 actions now? Thank you.

[@PowerPlatPros]

What about all Daraverse dataflows connectors in Power Automate pointing to DEV Environment, when move to production they sre stock in Dev. ?

[@SeanAstro]

When you deploy it will automatically repoint to the current environment for Dataverse actions in Power Automate. Power Automate can only point to the Dataverse environment it's deployed to. Unless you use the Legacy Dataverse connector. For SharePoint and other connectors you can use environmental variables, to not get stuck always pointing to Dev.

[@PowerPlatPros]

@@SeanAstro thanks for your help, my error is with "Refresh a dataflow" Connector. When move the solution from Dev to Prod, in prod these connector are pointing to Dev. Do I need to remove the unmanaged layer from solution then?

[@Untethered365]

@@PowerPlatPros unmanaged layers should definitely be removed if it won't break something, as a first step.

[@PowerPlatPros]

@@Untethered365 thanks for youe help!

[@sohitthakur6660]

​@@PowerPlatProsI think you faced the issue in the connection, it would be took the dev connection instead of prod during deployment, so for that case we should use environment variable i think , correct me if I am wrong

[@Loves-f3y]

Hmm, it ends with what I think is a runtime error. Just copy and rename a flow to have them all have unique functionality - in this case it is email addresses?

[@ChrisPosu]

Why doesn't use pipelines to move solutions between environments?

[@Untethered365]

They're great but if you don't understand these concepts the pipelines won't help.

[@ChrisPosu]

@@Untethered365 I agree and by the way great channel