Share This Post

D365 Updates

Upgrade of Dynamics 365 for Finance and Operations

This article explains the process of updating or upgrading to the latest release of Microsoft Dynamics 365 for Finance and Operations. It describes the overall process and supported scenarios, but it doesn’t provide detailed instructions for every step of the process.

  • Upgrade – The process of moving from one official release of F&O to the next release, for source environments prior to version 8.0. Some examples are the move from 7.1 to 7.3, or from 7.3 to 10.0.1. The process involves the setup of a free sandbox environment, code upgrade, and data upgrade.
  • Update – The process of applying a binary package to an environment to move it from 1 official release of the Finance and Operations to the next release, for source environments beginning with version 8.0. This process has lower downtime requirements and doesn’t involve data upgrade.

Paths to One Version

  • Self-Service Upgrade

To align the self-service upgrade process to support continuous updates, each new release will cause the previous release version to be discontinued.

For example, you have app version 7.3 with a platform update (PU) 23. Currently, the supported upgrade versions are 8.1.3 with PU 23, 10.0.0 with PU 24, and 10.0.1 with PU 25. When the next release, 10.0.2 with PU 26, is made generally available, it will be added to the available upgrade options, and 8.1.3 with PU 23 will be removed.

Because of this continuous process of adding a new version and removing the oldest version, we recommend that customers upgrade to the latest version that is available. In that way, you have two months in which you can upgrade your sandbox environment and then later upgrade your production environment to the same version.

If you choose to upgrade your sandbox environment to version 8.1.3 with PU 23 and Microsoft then releases version 10.0.2 with PU 26, so that version 8.1.3 with PU 23 is removed as an upgrade option, you will be blocked from upgrading your production environment. In this case, you must start over in the sandbox environment and upgrade to a newer supported version.

  • Rebuild and Update

Traditionally, moving to a newer application version has involved a rigorous upgrade that includes the deployment of additional virtual machines, code upgrade, data upgrade, and scheduling several days in advance with the Microsoft Dynamics Service Engineering (DSE) team. You will notice that we are making the uptake of the latest version simpler, and this will continue to improve over time.

The high-level process to update from version 8.0 to 10.0.X involves the following:

  1. Deploy 10.0.X developer and build the environments.
  2. Branch in the version control and remove any app hotfixes.
  3. Recompile custom extensions and/or ISV solutions.
  4. Produce a single software deployable package.
  5. Merge a deployable package with the 10.0.X binary update package.
  6. Deploy to target environments for validation.
  7. Deploy to Production.
  • Automatic Update

In Microsoft Dynamics Lifecycle Services (LCS), you can specify how and when you receive service updates from Microsoft for your Microsoft Dynamics 365 for Finance and Operations environments.

Only users (customers or partners) who are assigned to the Project owner role in LCS can configure updates. Additionally, updates can be configured only for implementation projects.

Follow these steps to change your update settings

  1. In LCS, in your implementation project, open the Project settings page.

    This page has a new tab that is named as the Update settings.

  2. On the Update settings tab, set the following configuration as you want:
  • Update environment – Select an alternate sandbox environment that should be updated before the production update.

By default, Microsoft 1st updates the Tier 2 Standard Acceptance Test (sandbox) environment that is included in the base offer. It then applies the update to the production environment. If you’ve purchased Tier 2 and higher sandbox add-on environments and want a different sandbox to be updated, you can use this field to change the default environment to an alternate environment.

  • Production environment update cadence – Choose the recurring cadence for the updates to your production environment. The sandbox environment that is chosen in the Update environment field will be updated 7 calendar days before the selected cadence. The following options are available:
      • Choose the cadence – Select whether to receive updates in the first, second, or third week of the month.
      • Select one of the three time-zones – Select the time zone that the production environment should be updated in Eastern Time (UTC – 5), Hong Kong Time (UTC + 8), or Greenwich Mean Time (UTC + 0).
      • Choose a day of the week: Select the day in the week when you want to receive updates.
      • Select a time slot: Select the time slot when you want to receive updates.

3. When you’ve finished setting the configuration options, select Save.

After you set the update environment and update cadence, Microsoft generates an updated calendar for the next six months. This calendar displays the exactly when the configured sandbox and production environments will be updated.

Therefore, you will know when to expect each update. To view the calendar, choose View update calendar link under the Production environment update cadence options. For more information, please contact us.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar