De-mystifying Versioning in Dynamics 365


As updates are deployed to the Dynamics 365 service, there are two separate versions that are tracked:

  • App Version

Application version represents the binary version that is deployed to the Dynamics 365 servers. These updates contain product improvements and bug fixes that are delivered through application code changes.

  • DB Version

Database version represents the version of the organization’s database. These updates contain customization changes to support new features, product enhancements, and bug fixes.

Why does the App Version and DB Version sometimes differ?

There are two primary scenarios where the App Version and DB Version will not match.

  1. App-only Update: As we continue to increase the frequency of updates to Dynamics 365, it is common for a release to only include application updates with no database updates required. In such a scenario, the application version will be incremented, but the DB version will remain the same.  On a subsequent release that involves both application and database changes, the versions will once again align.
  2. Update Sequence: During the update sequence, application servers are updated first, followed by the update of the organizations themselves. Multiple organizations are batched together and updated concurrently to speed up the overall release. Depending on when an organization is picked up for processing, the versions may not match during this window of time.

What should I do when the versions do not match?

As described in the scenarios above, it's entirely normal for the App Version and DB Version to occasionally differ.  The application is built specifically to support compatibility with previous database releases, so mismatched versions are generally (except very rare scenarios) not a cause for concern.

 

- Vinay Singh

Comments (0)

Skip to main content