Business Central spring 2019

Path: Business Central on-premises > Upgrade > Earlier versions > Business Central spring 2019 · tier official · system platform · narrative reviewed (checked by Opus)

Overview

This section describes how to upgrade to Business Central on-premises spring 2019 (v.14). The entry page, “Upgrading to On-Premises v.14”, explains that the path depends on the source version, with different routes for versions before NAV 2018. It splits the work into application code upgrade and data upgrade, for single-tenant or multitenant deployments.

The other pages cover each stage. “Upgrade Application Code” shows how to merge original, modified and target versions with PowerShell cmdlets. “Converting a Database” describes the technical upgrade, and “Upgrading the Data” covers the single-tenant data upgrade. Three quick reference checklists cover technical upgrade, single-tenant full upgrade and multitenant full upgrade. “Upgrade Considerations” and “Transitioning from Codeunit 1 to System Codeunits” cover changes that may affect custom code. “Install a cumulative update” covers updates within the version.

Start with “Upgrading to On-Premises v.14” to pick your path. Then read “Upgrade Considerations” and use the quick reference that matches your deployment mode as a checklist.

Key points

• The upgrade path depends on the source version. Versions before NAV 2018 follow different paths.
• Upgrade has two parts: application code upgrade and data upgrade. Each applies to single-tenant or multitenant deployments.
• Application code is merged with Merge-, Compare-, Update- and Export-NAVApplicationObject cmdlets. Conflicts are resolved in object text files.
• Technical upgrade converts the database, synchronizes the schema, converts reports to RDL and migrates V1 extensions to V2. A license must be uploaded.
• Data upgrade runs upgrade codeunits, synchronizes the schema, publishes extensions, generates symbols and imports or exports permission sets.
• Codeunit 1 is removed. System codeunits now hold event publishers, and the page maps old triggers to the new ones.
• Upgrade considerations include cloud migration, V1 to V2 extension conversion, CRM integration upgrade, MenuSuite search, profile customization and special characters in company names.
• Cumulative update installation covers downloading the package, updating platform components, importing application objects, publishing extensions and uploading the license.

Learn pages

• Converting a Database to Dynamics 365 Business Central - Technical Upgrade: Learn how to convert a database from one of the supported versions to Business Central version 14 as part of a technical upgrade.
• Install a cumulative update: This article describes the tasks required for getting the monthly cumulative update applied to your Dynamics 365 Business Central on-premises.
• Multitenant Technical Upgrade Quick Reference
• Single-Tenant Full Upgrade Quick Reference: Get an overview of the steps required to upgrade from one version of Business Central on-premises to the next.
• Technical Upgrade Quick Reference
• Transitioning from Codeunit 1 to System Codeunits: Learn how to convert your custom code as part of the upgrade to version 14 of Business Central.
• Upgrade Application Code: The article explains how to upgrade the application code to version 14 and how to merge code from different versions of the application.
• Upgrade Considerations: This article provides tips and considerations to prepare a solution when you are planning to upgrade Microsoft Dynamics 365 Business Central.
• Upgrading the Data to in Single-Tenant Deployment: This article describes the tasks required for upgrade the data to version 14 when you have a single-tenant deployment.
• Upgrading to On-Premises v.14: Gives an overview of the different upgrade paths to On-Premises Spring 2019 from older versions.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.