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
I understand we should using extension not over-layering in development.
However, is it a must to create new model? Can I develop under the standard Microsoft model using extension?
You can't add anything to the standard Microsoft packages / models. So yes, you must create your own package and model for your extensions.
The whole package is compiled to one DLL in the build process. You can't add anything that would change the standard DLLs. Instead your extensions must be built to another DLL that is installed alongside the standard ones.
You should use an own new model. It is not possible to use the Microsoft models as they have been locked and exist in a different application layer (which is still part of the AOT layering concept).
To further clarify, we would advise against creating a new package or model for EACH extension you're doing. Yes you need to create your own, BUT you want to minimize the amount of new packages/models you create and keep it simple.
If you're asking yourself, should I be using more than one package/model, the answer is probably no. When you have some sort of need to have multiple packages or models, you'll know :-)
Business Applications communities