Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
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 2 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
In some cases, your customer or partner will need to customize your application using extensions, but may find themselves having to extend an element that is already an extension. In other words, if you extend Microsoft metadata and your customer wants to extend your extension, will they be able to do so?
Developers can follow the procedure described in the example below to extend an extension, it works in many scenarios.
Let us assume you are working on the “Fleet Management Extension” package and want to first add a new field group to the FMRental table. The FMRental table is in the fleet management model. Here’s what you would do:
You have distributed your solution (the "Fleet Management Extension" package) to a third party that would like to extend MyNewFieldGroup, here’s what they would do.
The main thing to keep in mind is that you always extend the base element, even if you have a dependency on another extension.
Business Applications communities