Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
We have a highly customized Contact ribbon/command bar for our customer in a multi tenant CRM 2015 environment. In our dev org, we used the RibbonWorkbench2013 tool to remove some buttons added by other vendors. We added the Contact entity to its own solution, exported it and imported it into an existing Production org successfully. If we try to import this solution into a brand new org, the import fails with error::
The ribbon item 'Mscrm.Isv.contact.HomepageGrid' is dependent on <DisplayRule Id="Mscrm.Isv.contact.HomepageGrid" />
We can successfully import this solution into the new org if we manually adjust the ribbondiffxml by removing the CommandID and Display Rule associated with Mscrm.Isv.contact.HomepageGrid. If we try to export that contact solution and import back into our Dev org, it fails with the same error. If we adjust the contact ribbondiffxml manually back to the default (with no customizations), and import back into our Dev org, the import fails again with the same error.
How can we remove this dependency error from our Dev org so we don't run into this issue again?
Thanks for any feedback
Hi you will need to review the Display rules on your customised contact buttons as there is one that has a reference added that you will need to do before exporting the solution, as well as command bar also review the ribbon just in case
Best Wishes, Raz
Thanks for the feedback. I initially tried to remove the dependency from within the ribbondiffxml, but it continued to give the above error. Attempting to import the default ribbon also gave the error. Is there somewhere else within the XML that we need to look?
Business Applications communities