The process for deploying, promoting and applying hot fixes to VeloCITY 365 follows a well-documented path from Development to Production. It is expected this methodology will be followed with separate environments for each phase of the development cycle. All new work or changes are made within the Development Environment. The changes are promoted to the Test Environment for testing and approval/rejection. Once these changes have been approved, they are promoted to the Production Environment. This path not only ensures the changes to the product are successful applied, it also ensures the deployment/promotion process is complete and produces the desired results.

When planning for an upgrade, promotion or hotfix there are 2 categories of information that needs to be considered, namely customizations and data.

  • Customizations are changes that have been made to the Dynamics 365 platform, i.e., entities, option sets, dashboards.
  • Data are business records, i.e., contacts, cases, information that drives the portal (Content Snippets, Web Links etc.)

Safe

Use Caution

Avoid

Changes to content are considered safe. Examples include:
Content to the Deflection content on an Interaction Type
Content within names, titles, text or summaries on Web Pages
Content within titles, descriptions or URLs of Web Links
Values on Content Snippets
Values on Site Settings

Changes to the Production environment that involve the creation of new application data as all actions are immediate, are visible to a large audience and having incorrect or incomplete data can have disastrous consequences.

Removing any application data as recovery is time consuming and not always possible.

When agreeing to a Hot Fix, consideration must be given to how the change will be merged back into the Development environment. For large and/or complex changes, the recommended methodology is to use Microsoft’s Configuration Migration Tool. The conditions that need to be considered include:

  • New records must be copied back to the Development environment using an ID- matching data copy tool
  • Content changes can be copied back to the Development environment using copy-paste or ID-matching data copy tool
  • Schema (customizations) changes should be copied back to the Development environment using a transport solution
  • Customizations should be copied back to the Development environment using a transport solution or by manual reproduction (Not recommended, but possible)
  • A subsequent deployment is needed from the Development environment to the Test/UAT environment