Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides important information and tips for things to consider when you prepare to upgrade to Business Central 2022 Release Wave 2, version 21. The information that's relevant for you will depend on which version you're upgrading from, and how much your solution differs from the Business Central base application.
Migrate from Dynamics NAV to Business Central online
You can upgrade to Business Central online from supported versions of Business Central on-premises, as long as your application customization is handled by extensions.
The process consists of two parts:
- Convert non-standard functionality and customizations to apps and per-tenant extensions. For more information, see Deploying a Tenant Customization.
- Run the cloud migration tool as described in Migrate On-Premises Data to Business Central Online, and then switch to use Business Central online going forward.
New and changed application and platform features
There are several new and changed application features available in version 21 for users, administrators, and developers. For an overview of these features, see What's new and planned for Dynamics 365 Business Central.
To take advantage of all these features, you'll have to perform an application code upgrade, not just a technical (platform) upgrade.
Deprecated or redesigned functionality
Business Central occasionally deprecates features in application and platform. In most cases, features are replaced by more modern and sustainable features. If you're upgrading a solution that depends on the deprecated or changes functionality, you may have to change application code as part of the upgrade process.
For example, sometimes code has been refactored so that fields are no longer used. Or the functionality is moved from the base application to an extension. Typically, if you have custom extension code that depends on these fields, you'll have to create a new version of the extension to handle the change.
Learn more about the deprecated features at:
- Deprecated Features in Application
- Deprecated Features in the Platform - Clients, Server, and Database
- Deprecated Fields, and Fields Marked as Obsolete
Important deployment-related changes
The default port for client services port for Business Central Server has been changed to 7085 instead of 7046. You can still use 7046, but you'll have to change the port number in the Business Central Server instance configuration. For more information, see Configuring Business Central Server.
Server principle names (SPN) are no longer supported by .NET Core. This change has affected the delegation from the Business Central Web Server to the Business Central Server when they're on different computers.
The affected scenarios are described in Deploying Business Central in a Two-Computer Topology and Deploying Business Central in a Three-Computer Topology.
For more information about how to set up delegation, see Configuring Delegation for Business Central Web Server. You can do this task anytime, but after you upgrade, users won't be able to sign in to the web client until you do.
Permissions and permission sets
Business Central 2021 release wave 1 (v18) introduced a new model for permissions. In previous versions, permission sets and permissions are defined only as data, which means they're stored in the tables of the application and tenant databases. Permission sets and permissions can now be defined in AL code as objects and packaged in extensions. This new model is the recommended model. To learn more, see Entitlements and Permissions.
- If you've already made the transition to the new permissions model in your current solution, then there's no extra work related to permission sets required for upgrade.
- If you're upgrading solution that hasn't transitioned to the new permissions model, we recommend that you do. However, you can continue using the legacy model. Whichever model you choose, there's permission-related tasks you'll have to complete as part of upgrade. Learn more at Upgrading Permissions Sets and Permissions
Report platform
Version 20 introduced a new report rendering model. Previously, report rendering was done by the application. Now, by default, report rendering is done by the platform. In support of this new model, various changes have been made tht affect upgrade from version 19 and earlier. If you're upgrading from version 20, the solution should already include the necessary changes.
Learn more at Upgrading reports.
Related information
Upgrading the Application Code
Upgrading the Data
Deprecated Fields, and Fields Marked as Obsolete