Skip to main content

Business Central Upgrade Error - What happens, How critical is it and how to handle it

Problem Statement:

After the launch of BC v16 in April 2020, I got an email stating htat the BC Production Upgrade will be scheduled to in June 2020.

A couple of days passed by and all the Users started getting this image. 
Take Action Now - Your Business Central Tenant Cannot be updated to BC 16
Take Action Now - Your Business Central Tenant Cannot be updated to BC 16


Although I certainly appreciate having this image on top as notification everytime you login into Business Central, I have gotten feedback from my customers stating that this creates some sort of tension and discouragment between the Users.

Pre-requisites:

  • Understanding of how to Upgrade Business Central
  • Knowledge of Notification Recepients
  • Understanding of changes code from BC vX to BC vY

Solution:

1. Find out which extension is stopping BC from being upgraded. Generally this is available through emails that have been received from Microsoft.



2. Deprecate the old code and refactor to latest version by using the latest version of  AL Language Extension and Business Central Sandbox.

3. Create a new Production with the latest version through Admin Center to test if your app can be deployed.
Refer

Conclusion:

If you miss upgrading your Business Central Tenant, your Extension will be forcefully uninstalled within after 90 days of this error. Your Business Central Tenant will be upgraded to the latest version and then you will manually have to upgrade your extension and install it.

Note that this mostly will not erase your extensions data by your extension related functionalities will not be usable.

Please feel free to ask and take help of Microsoft Support by raising support case through Admin Center.


Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations#online https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths https://www.sauravdhyani.com/2018/10/msdyn365bc-data-upgrade-to-microsoft.html https://olisterr.blogspot.com/2022/03/how-to-upgrade-data-from-microsoft.html https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-permissions Demonstration: 1. Install Business