Customisation

Customisation

This section explains how to extend Dynamics 365 in a simple and predictable way, starting with a configuration‑first approach. Teams should use the platform’s built‑in features before moving to low‑code or pro‑code options to keep solutions easy to support and maintain.

It outlines when to use Business Rules or JavaScript: Business Rules for straightforward form logic, and JavaScript only when more complex behaviour is needed.

It also explains how to choose between Power Automate and plugins. Power Automate is suitable for basic automation and simple integrations, while plugins are used for synchronous or more complex logic.

Finally, the section sets expectations for pro‑code development, covering coding standards, maintainability and ensuring custom logic fits cleanly within the service’s solution structure.

In this section

• Configuration, Low‑code, Pro‑code

  Implementing changes using platform configuration first, using low‑code only where needed and reserving pro‑code for scenarios the platform cannot support.

• JavaScript vs Business Rules

  When to use Business Rules for simple client‑side logic and validation, and use JavaScript where more advanced or conditional behaviour is required.

• Power Automate

  Use Power Automate for lightweight automation or simple integration tasks that do not require synchronous execution.

• Plugins

  Plugins are for complex automation, advanced logic, or scenarios requiring synchronous or tightly controlled server‑side processing.

• Pro Code Coding Standards

  Established coding standards and patterns to all pro‑code components to ensure maintainability, reliability and consistency across services.