Dynamics 365 — The cost of manual deployments activities

We can create a customisation that meet customer requirements quickly but they must be maintainable and moved between environments without manual tasks or you create a growing maintenance backlog. The creation of a customisation is only half the work needed.

Lets walk through an example which will show the cost in time of manual data and customisations.

Scenario

We create a workflow which sends an email to account when a certain field is updated. We create a Workflow in Dynamics 365 and manually create the account in each environment.

You might see this as not being to bad and wondering why Hosk going on about keeping guids in SYNC

• When it comes to guids, take your lead from the boy band NSYNC #HoskWisdom
• When guids are out of sync, manual work is needed every time you deploy #HoskWisdom

or the recent blog posts — Dynamics 365 — Document templates, guids and workflows

What happens next

The account is manually created in

• DEV
• QA
• Training
• UAT
• PreProduction