Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I know the subject is known and I know the limitations on the subject, however I would still like to ask you for your opinions on the best practices of my use case:
I have a Prod environment on which a mixture of managed and unmanaged solutions coexist. Obviously, I don't have a DEV environment with all the unsupported solutions and I don't have the unsupported solutions in ZIP somewhere either.
My need would be to be able to export an Unmanaged solution from my Prod environment (therefore from the Managed solutions) in order to be able to recreate an unmanaged Dev environment, aligned with the prod.
I know that by definition it is no longer possible to achieve this, but how impossible is it? Is there a procedure to do this? Maybe by manipulating the XML, or via a script / tools?
Do you have an idea ? experiences there? which could unblock us ... Otherwise I do not see how to continue the developments on this Managed environment ...
Thanks a lot !
As far as I know, there's no way to retrieve the unmanaged part from a managed solution. Perhaps, you can create a new unmanaged solution that requires your managed solution to be part of it. That means your unmanaged solution would have a dependency on your managed solution, and any time you want to migrate your unManaged to another environment, you have to remember to include it as part of the deployment.
Hope it helps.
easiest thing to do in your situation is to recreate (by copying) the development instance starting from the production one, yes you will still have managed solutions but because your systems will be aligned (to the same layer) any further customization should work.
Hi @Guido Preite,
Not sure to understand, you propose to back up / restore a new Env from the Prod. This env will be the New DEV. But Managed solutions (layers) on it won't be a problem to continue to extend it with new customizations ?
Is it a "possible/supported" scenario in term of ALM ? It could raise some other blocking behaviour ?
What about if we want to export solutions and build a new blank env for a sub scope of the application / for a new project... We will have some dependencies issues because of the managed layers... ?
Maybe some others situations could exists ? What is your opinion ?
Hi Daniel, Thx for your answer. Agreed with you ! Not ideal :(
Business Applications communities