Extension-Based

Development in
Dynamics 365
What are Models?
Models are sort of containers that consist
of code - code which tells Dynamics 365
how to behave & what to do when the
user interacts with the system.

Code

Classes, tables,
reports etc

Model
Development in AX2012

In Dynamics AX 2012 you could go ahead

and directly change the default code to
your liking. While this was really
convenient it caused several issues.

Customizations
in base code

AX2012
Base Code
This way of development was
troublesome for AX itself and
the customizations.

WHY?

Continue reading
Issues in AX2012
The code base for Ax 2012 was too
huge to maintain.
Direct changes to application code
caused bugs and errors.
During hotfixes & updates the
customizations interfered with the
process.
Custom code isolation was a big issue.

AX has crashed.
Microsoft released Dynamics
365 and enitirely changed how
customizations were to be
made to the system.

HOW?

Continue reading
What are Extensions?
With the advent of D365, Extension based
development came in to practice.
Extensions are like add-ons. You create
these to change how a particular part of
D365 works and behaves.

Extensions are like lego

blocks. Once created they can
be attached to D365 to make
D365 work and look different.

D365
To apply the customizations
and extensions from the
extension to the standard code,
Dynamics 365 uses a feature
called Chain of Command.

WHAT IS IT?

Continue reading
Chain of Command
Chain of command is a feature in
Dynamics 365 that lets developers
change how the application works
without having to change the original
code.
How it Works?
Chain of command intercepts the
standard application code at predefined
extension points and allows the
extension code to execute:

BEFORE
AFTER
INSTEAD

of the standard code.

This means that developers can modify

the behavior of the application without
modifying the standard code directly
Like and repost if you found this
helpful.

Follow me for more content on

Dynamics 365 development.