Skip to main content

Few things that can save you a lot of hassle in Per Tenant Extension Code Upgrade in Microsoft Dynamics 365 Business Central Wave 2 (version 15) Upgrade

Problem Statement:

With a change in Business Central Version from Version 14 to Version 15, I had noticed a few things got deprecated. Instead, these functions where deprecated and overloaded which why function definition remains the same but the parameters change.


In this blog, let us discuss the changes in Business Central BaseApp coding that can possibly break your extension and prevent you from upgrading. 

Also, I will be discussing the list data type introduced since the 2019 Wave 2 release.


Microsoft Dynamics Business Central Version 14
Microsoft Dynamics Business Central Version 15

Books & References:

List DataType


In this blog, let us take an emailing codeunit as a use-case.

1. Change in Variable Declaration:
Earlier in Emailing functionality, we made use of Text to store the Email. For multiple emails, we would append a  SEMICOLON ';' after each recipient.
Text Variable Declaration

Now, Text is replaced by List of Text and we don't need to add SEMICOLON ';' in between
List of Text  variable declaration
2. Change in Codes and functions:
 With respect to the SMTP Mail codeunit, the function is deprecated and overloaded with another function. Also, the deprecated function uses the newly created function
Change in functions

3. Fixing the code:

After the change of the standard codeunit, your functionality code also requires change so that even if the function in support right now but it can be deprecated pretty soon and that your upgrade process should be smooth.
Errors in Version 14 Extension Code
The fix for this is as below.
Old Email Appending Code replaced with ListVariable.Add() function
Change in function parameters

4. List DataType:
List Data Type is pretty straightforward in terms of usage.
You can refer

The illustrated examples can help you understand the functionality pretty easily.

Just to add, I have copied the syntax from
you can add and retrieve data using Get() and Set() methods.

Also, could this mean that Lists are replacing arrays in the near future??
Let me know your comments.

5. TempBlob is marked for removal:
A simple solution is to replace TempBlob record with TempBlob codeunit.
Basically, all the functions inside TempBlob tables will be copied in TempBlob Codeunit.

6. Deploying the app:
In order to deploy your app to version 15, you will need to change the app.json file and deploy as the next major version.

Refer Dmitry Katson's blog


In this blog, I have attempted to give a glimpse of what I had to change in order to prevent my package from breaking in Business Central version 15 Upgrade.
Also, if I find a few more changes that can break your code I will post it in continuation of this blog.

In the upcoming blogs, I'm planning to write about the new DataTypes that have been added to Microsoft Dynamics Business Central since 2019  Wave 2 Version 15.

Hope this helps :)


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: 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

Business Central Environment Blinking after update to v20

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox :<SandboxEnvironmentName>/?sandbox=true Production :<ProductionEnvironmentName>/ If you URL like or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta