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

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe