Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We are actually reorganizing our CRM customizations. We have one main solution which is containing all the customizations and now we would like to split them by technical matters.
So now on our development instance, we have 4 unmanaged solutions that we would like to publish on tests instance which have the old solution organization.
We plan to do the following:
-> Export the 4 solutions to managed.
-> Import them to test instance.
-> Uninstall the old solution from test instance.
I have a doubt concerning that procedure. Will it break something ?
At some point we'll have the same customizations from different solutions. What do you think ?
In order to avoid data loss, your procedure is correct.
You might face some dependency issues when doing it, but it is the only way to ensure that nothing is lost.
As long as all your customizations from the main solution are all on the 4 different solutions then it shouldn't break anything.
Business Applications communities