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.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
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
If i delete the managed solution(cloned solution latest version) imported to Production, does it delete the old data from the environment?
Scenario is as follows:
Development : Latest cloned Solution is Solution 220.127.116.11
Production: Old Solution 18.104.22.168 plus 3 patches 22.214.171.124, 126.96.36.199, 188.8.131.52
UAT: Old Solution 184.108.40.206 plus 3 patches 220.127.116.11, 18.104.22.168, 22.214.171.124
I have recently cloned the solution in DEV environment and imported the managed new version in UAT and have to do the same in Production.
The issue appeared when importing new version in UAT there were some dependency issues due to which the old solutions were not deleted and in fact i was left with
Cloned Solution(126.96.36.199), 3patches (188.8.131.52, 184.108.40.206, 220.127.116.11) and old solution(18.104.22.168) in UAT. So i deleted the imported managed cloned solution in UAT before fixing the dependency errors in DEV, after which it worked perfectly.
Now my worry is if same happens in Production will it be safe to remove the latest version of managed solution, will it remove data as well, since it will contain all components of every patch and base solution?
What should be the right way to deal with if I am left with latest version (but with error) in addition to old versions.
If you delete the managed solution then system will delete all its components, please find more information using at https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/introduction-solutions#managed-solutions and https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/uninstall-delete-solution. Thank you.
It is not best practices to remove/delete managed components from production.
It will remove all the customisation done from the system. Production will have real time data so data will also gets removed. It will be Chaos.
Create new solution add all the necessary components and import to production.
Thanks for your reply.
The situation that i am facing is not a simple import and export issue, I have cloned the solution in DEV and then i am importing it to Apply the upgrade in Production.
When i did this in UAT i had some issues in Applying the upgrade which automatically left me with the New version plus the old version in UAT but it being UAT i easily removed the New version fixed the issues and reimported to apply the upgrade.
So are you suggesting, if in Production i get into similar situation as UAT, i should create a new solution and all all the components and import ? but in that case what happens to the old version, Latest version?
I am a bit confused.
What I am saying is you should not delete solution in prod, it is not a suggested one.
Yes, create new solution include necessary components and import to prod. All your customisation will remain, both new and old.
If it a same solution you need to worry about upgrading the solution. Maintain or overwrite the customisation. Since it is new solution, you will not face any issues.
Business Applications communities