Do you know how to correctly use the terms Configuration, Customization and Extending in the CRM context?
  v1.0 Posted at 1/07/2013 3:10 PM by Mehmet Ozdemir

It is important to use consistent language when talking about changes made to a CRM environment. The terms configuration and customization are sometimes used interchangeably.  It is clearer to use the following to differentiate them: Configuration, Customization and Extending.


Configuration applies to any changes made to existing options available within the default installation of CRM, examples might include changing the default currency from USD to AUD or the way emails are sent; using the Email Router instead of Outlook etc.
Configuration applies to objects like: Business Units, Security Roles, Users, Teams, Field Security, Auditing, and Solutions

Customization is anything that can be done within CRM without resorting to the SDK or external code. Adding new fields to an existing entity, creating new entities, option sets, reports etc.
Customization would apply to: Fields, Entities, Relationships, Forms, Views, and Charts, Workflows, Imports etc.

Extending is anything that involves writing custom code. This could be a plug-in (SDK) or JavaScript code (external code).

See the TFS​ rule for correct definitions.

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: