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 Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I want to make sure we are not missing out on new features and functionality. I may make the case to our users that we should try some of the new features, and for that, I would need to be able to show them. I was thinking that the ribbon customization xml may over-write all access to the OOB ribbons. SiteMap, I have more confidence because MS usually has multiple SiteMaps (the "app" sitemap for example would be there even if the default one was customized). Form layout - again not too concerned as I can probably work that out for myself. I guess I'm mainly worried about the ribbons?
If I import our existing database into the upgraded 9.0 environment, will the out of the box ribbons, sitemaps, and forms be there alongside my customized option, or will I be over-writing all of the new stuff with my old stuff? Does it literally over-write the organization with old 8.2 stuff and then just update what's there, or does it merge it in?
I suppose the other option is that you move over customizations selectively (by solution import or rebuilding), but then you'd also have to migrate all the data. even though we are only using the customer service related entities, that feels like a very scary option - worried about data getting unrelated to each other or that the case numbers won't come over. But maybe some experiences/advice if anyone has gone that route and why they saw a benefit in it.
Hello, in the newest versions of Dynamics we have a concept called solution layers, which basically means that a component can have multiple definitions for different solutions.
Now when it comes to Ribbon specifically, the out of the box buttons are always going to be on the System layer, and then the customizations you import for those buttons will appear above it on your own layers.
In addition to this, working with Ribbon in version 9 has become much easier, with the addition of new troubleshooting tools such as the command checker, which allow you to easily discover what is happening with your buttons.
Business Applications communities