Extensibility home page
Microsoft Dynamics 365 for Finance and Operations is extensively customized by partners, value added resellers (VARs), and even some customers. The ability to customize the product is a strength that has historically been supported through overlayering of the application code. The move to the cloud, together with more agile servicing and frequent updates, requires a less intrusive customization model, so that updates are less likely to affect custom solutions. This new model is called extensibility and has replaced customization through overlayering.
Extensibility is the only customization framework in Finance and Operations and Microsoft Dynamics 365 for Retail. Overlayering isn't supported.
These introductory topics contain general information about customization. This information includes information about when the transition occurs from customization through overlayering to a purely extension-based model. These topics also explain how to log extensibility requests to Microsoft, and provide answers to frequently asked questions (FAQ).
This section lists the extensibility-related updates that have been made since July 2017.
- Extensibility changes in Dynamics 365 for Finance and Operations, Enterprise edition (July 2017)
- Extensibility changes in Dynamics 365 for Finance and Operations, Enterprise edition 7.3
- Extensibility changes in Dynamics 365 for Finance and Operations release 8.0
The topics in this section will help you start to build extensions. They will also help you migrate solutions that are currently based on overlayered code to extension-based solutions. This section includes hands-on labs that walk you through simple customizations.
- Migrate from overlayering to extensions
- Customize model elements using extensions (tutorial)
- Customization: overlayering and extensions
Fundamentals on extensions
This section includes fundamentals, principles, and practices for making extensions. The guiding principles in these topics discuss how customization must be approached through extensions. These principles include naming guidelines. Additionally, these topics discuss the foundation framework, such as extensions and chain of command.
- Intrusive customizations
- Class extensions
- Class extension: Method wrapping and Chain of Command
- Naming guidelines
- Relax model restrictions to enable the refactoring of over-layering into extensions
How do I create extensions?
This sections includes "How do I?" topics that explain how to customize specific object types or code. Most of these topics are brief and to the point. Because there are many topics here, it might be practical to search for a specific topic.
- Register a subclass for factory methods
- Respond with EventHandlerResult
- Extend the RunBase class
- Use delegates to customize Application startup
- Modify an existing field in a table
- Add a new field to an existing table
- Add an index to an existing table
- Add a relation to an existing table
- Modify properties on an existing table
- Add a method to a table
- Perform business actions throughout the lifecycle of a table record
Information about customization is also shared through blogs where various topics are discussed. This section includes reference to some of these blogs.
- Extending Dynamics 365 for Finance and Operations
- Extending class state
- Extension methods
- Extensible base enumerations
- Static event subscription
- Responding through delegates
- Subscribing to onValidatingWrite
- Extending inventory dimensions
- Embrace the extensions mindset with Dynamics 365 for Finance and Operations
How do I create an extensible solution?
This section includes some best practices on how to create/make your solution extensible, so that consumers of your code can extend your solution.
- Writing extensible code
- Extended data types
- Extensible enums
- Extensibility attributes for methods
When you make your solution extensible, you also help guarantee that you won't break those extension points later. For pointers that can help you avoid breaking your consumers, see Breaking changes.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.