The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Better Together T-shirt Design Contest
We're starting a “Better Together” T-shirt design contest. The theme is "Powerful alone. Better together," and we want to see your best T-shirt designs that encompass all 5 products in the family: Microsoft Dynamics 365, Power BI, Power Apps, Power Automate, and Power Virtual Agents. | Read More about T-Shirt Design Contest
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
In Dynamics 365, to delete any component, you must remove/delete all the dependencies of the component which you want to delete. For e.g. If you want to delete custom entity called Configuration, you will need to delete/remove all the dependencies of the component which are dependent on Configuration entity.
Now many times users face problems in finding where can I get the list of dependent components? It’s easy to just say Open Default Solution > Go to Entities > Select the Entity > Click on Show Dependencies. Yes. That’s absolutely correct.
Now the problem is when we don’t understand the list which is shown by CRM. This blog explains tricky component which we don’t find directly.
We cannot easily identify highlighted components from above image because of below reasons:
When I investigated more on this issue, I found that there was a Business Rule which was registered on the entity and had scope as Entity. This was causing the issue.
I deactivated the business rule and deleted the same and the highlighted components got removed from the dependencies list.
Business Applications communities