Side by side comparison of extension approach in Microsoft Dynamics 365 Finance and Operations apps
|
Event Handlers (broadcast/non-sequential) |
Delegates (Sequential/Controlled trigger) |
Plugins |
|
Framework/Standard
Platform defined
Latest eventing approach for all extension purpose
Events node in VS Application explorer (design mode)
|
Intentional hooks defined in application
Purpose built (similar to events) to access functionality from lower package to elements in higher package (e.g. AppPlatform accessing something in AppSuite) |
Class Factory pattern to alter base functionality using abstract classes or interfaces.
Only for code. |
|
Pre/Post (AX 2012 XPP events on base methods)
Application defined
(for backward compatibility) |
|
|
|
*: To chain events, one can create all of them in a single class and list them sequentially. (in multi-developer environment would need code merging as each developer needs to create their own objects) |
|
|

Like
Report
*This post is locked for comments