Dynamics 365 Deployment Best Practice Guide
Microsoft Dynamics 365 is a leading line of enterprise resource planning (ERP) and customer relationship management (CRM) applications. With the platform’s high business impact, it is critical for enterprise leaders to follow best practices. In the past five years, we have deployed Dynamics 365 over 100 times for our Fortune 500 customers. Here are the eight best practices we use to optimize every deployment.
- Avoid broken references after deployment
- Import multiple files at once with .zip
- Include only required fields in data import files
- Deactivate relevant plugins/workflows before bulk updating records
- Enable admin mode on your target environment during deployment
- Include a user-friendly message while in admin-mode
- Back up the environment before deployment
- Run a test in a cloned production environment prior to production deployment
Maintain the same GUIDs across environments for records referenced in workflows/views. Use custom actions to parameterize the referenced records instead of directly referencing a record in the workflow.
Individually importing multiple data files is time-consuming and requires the files to be imported in the correct order to resolve inter-file column references. When you zip multiple files together for import, you save time and don’t have to worry about import order; Dynamics 365 takes care of it for you.
Including unnecessary fields in the data import file increases import time and may trigger workflows/plugins registered on those fields. For example, to update a contact address, don’t include unnecessary fields like first and last name in the import file.
To update data as part of data migration activities without triggering business logic, deactivate plugins/workflows registered on the entities present in import file. This reduces import time.
Admin mode locks the environment for all users, meaning only system administrators can access the environment. Enabling admin mode during deployment ensures that data is not compromised by unplanned changes. If an error occurs, data can be restored to previous versions. Note: Admin mode cannot be enabled in the production environment. If you are not permitted to convert the environment to a sandbox, use the global notification method to add a form.
During deployment, the system may be slow. This is why we recommended locking the system for end users. Messages inform end users that the environment is down due to planned activities and will return after the indicated duration. Clear messages avoid support tickets from confused end users.
Backups ensure that the system can be restored to its pre-deployment state in case a deployment failure occurs. Backups are faster than creating a copy of the environment. Note: When an environment is restored to an earlier state, the Data Export Service profile needs to be re-established to synchronize the Dynamics 365 data to Azure SQL.
Tests enable team members to prepare a mitigation plan. Issues can be proactively flagged and resolved, mitigating end-user impact.
- Invoke custom actions from a workflow – Microsoft, last updated February 15, 2022
Create a Single Source of Truth with Dynamics 365
Learn More →