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.
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.
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!
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.
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
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?
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.
@@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?
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.
Thank you! I can't wait until copilot can generate animations.
Excellent explanation. The visuals and guided example really help make it real rather than the usual reams of text / theory
The visuals took forever but I couldn't find another way to explain it.
@@SeanAstro I’d say well worth the effort 👌
Professional video. Thanks for sharing. I really like the format and how the information is presented.
Thank you! It was the only I could think to make it so it made sense
Such a good video. very clear.
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.
Awesome! I'm so glad it helped. I was trying to help make it visually easy cause it is tricky :)
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!
Absolutely thanks Tiago!
All signal, zero noise.
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.
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
Customization will be gone and data being gone depends on what kind of customization it was.
Good explanation 😃
How abd what is the best approach for cross tenants migration of flows and apps?
I've got a video on best practices in deployments coming soon!
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?
What about all Daraverse dataflows connectors in Power Automate pointing to DEV Environment, when move to production they sre stock in Dev. ?
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.
@@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?
@@PowerPlatPros unmanaged layers should definitely be removed if it won't break something, as a first step.
@@Untethered365 thanks for youe help!
Why doesn't use pipelines to move solutions between environments?
They're great but if you don't understand these concepts the pipelines won't help.
@@Untethered365 I agree and by the way great channel