Dynamics 365 Commerce component versioning requirements

This topic provides an overview of the component versioning requirements and dependencies for all components in the Microsoft Dynamics 365 Commerce ecosystem.

Overview

The following illustration shows an overview of Dynamics 365 Commerce components and corresponding versioning requirements and dependencies.

Dynamics 365 Commerce Component versioning requirements and dependencies

Component dependencies

Service updates

To ensure compatibility between all Commerce components that are serviced and deployed by customers and partners, you must follow several versioning dependencies during servicing updates. The following list describes all these dependencies.

  • Commerce headquarters and Finance and Operations apps must be on the same version as, or a newer version than, Commerce Scale Unit (both cloud and self-hosted).

    For example, if Commerce headquarters and Finance and Operations apps are on version 10.0.10, Commerce Scale Unit must be on version 10.0.10 or earlier (for example, 10.0.9 or 10.0.8).

  • Commerce Scale Unit must be on the same version as, or a newer version than, Modern Point of Sale (POS), Hardware Station, and the Commerce software development kit (SDK) and associated local site configurations (such as modules, data actions, and themes).

    For example, if Commerce Scale Unit is on version 10.0.10, Modern POS, Hardware Station, and the Commerce storefront must be on version 10.0.10 or earlier (for example, 10.0.9 or 10.0.8).

  • Extension packages must be compiled against the same version as, or a newer version than, the target component that the extension applies to.

    For example, if the deployed Commerce Scale Unit is on version 10.0.10, the corresponding extension packages must be compiled against version 10.0.10 or earlier (for example, 10.0.10 or 10.0.9).

Quality updates

During quality updates, no specific versioning requirements must be followed for each Commerce component, besides what is required for service updates.

Current supported versions

The following table describes the current supported versions of various Commerce components as of October 2nd, 2020.

Component Latest available release (first release available in Sandbox) Latest available component version number (first release available in Sandbox) Earliest supported release Earliest supported component version number
Finance and Operations apps 10.0.14 10.0.14 10.0.10 10.0.10
Commerce Scale Unit (cloud-hosted) 10.0.14 9.24 10.0.10 9.20
Commerce module library 10.0.14 9.24 10.0.10 9.20
Commerce Scale Unit (self-hosted) 10.0.14 9.24 10.0.6 9.16
Modern POS 10.0.14 9.24 10.0.6 9.16
Hardware Station 10.0.14 9.24 10.0.6 9.16

One Version requirements

Commerce components follow the same One Version service updates that were announced in July 2018, and also the subsequently published flexible service updates for Finance and Operations apps that were announced in June 2019. For more information, see One Version service updates FAQ.

Cloud components

Customers can pause up to three consecutive updates across the following components. (Three updates correspond to approximately six calendar months.)

  • Commerce headquarters and Finance and Operations apps
  • Commerce Scale Unit (cloud-hosted)
  • Commerce SDK and associated local site configurations (such as modules, data actions, and themes)

For example, customers who are currently on version 10.0.2 can pause updates to versions 10.0.3, 10.0.4, and 10.0.5. However, they must then update to version 10.0.6. In this scenario, after version 10.0.7 becomes available, version 10.0.2 is no longer supported.

In-store components

Customers can pause up to seven consecutive updates across the following components. (Seven updates correspond to approximately twelve calendar months.)

  • Commerce Scale Unit (in-store hosted)
  • Modern POS
  • Hardware Station

For example, customers who are currently on version 10.0.2 can pause updates to versions 10.0.3 through 10.0.9. However, they must then update to version 10.0.10. In this scenario, after version 10.0.11 becomes available, version 10.0.2 is no longer supported.

Additional resources

One Version service updates

For more information about One Version service updates, see the following resources:

Component selection

For more information about how to select the correct components to meet your needs, see the following topics:

Servicing instructions

For more information about how to service individual components that are described in this topic, see the following topics:

Extensibility and packing

For more information about serviceability for extensions, see Create deployable packages.