Dynamics 365 Configuration vs Customisation

When creating a new system in Dynamics 365, there are two potential ways of implementing, configuration and customisation.  At Ceox, we prefer to configure as much as we can, only customising when customers require it to meet their requirements.  Here are some of the reasons we prefer customisation over configuration:

• It future proofs against Dynamics 365 upgrades, by using inbuilt configuration it’s much less likely that an update to the core Dynamics 365 platform will break the solution.

• It is usually quicker to build the solution using configuration rather than customisation.

• It fits in with the Dynamics 365 UX design ensuring the user has a consistent experience throughout the application (and with the broader Microsoft applications).

Having listed all the reasons why we prefer configuration, occasionally the required functionality can’t be provided by Dynamics 365 and in that instance we’ll use customisation to build the solution.