Skip to main content

Enable AL and C/AL side by side for NAV Upgraded Database to Business Central


Now that NAV 2017 Database is upgraded to Business Central v14 (Refer link), it's time to connect your AL Development with your Business Central environment.
One of the issues with this approach is that NAV Database does not have the symbols generated.


- Upgraded DB from NAV to BC
- VS Code & AL Language Extension
- finsql.exe
- Business Central On-Premise with Windows Client


1. Connect VS Code to Business Central Database:
- Ensure that in Business Central Administration > Development > Enable Development Service Endpoint and Enable Debugging and Enable loading application symbol references at startup.
Enable Development in Business Central Administration 

- Ensure that the launch.json file in your project corresponds to your Business Central On-Premise Server
VS Code Configuration and issues.

2. Check if Symbols are present in the Database:
After running the Get-NAVAppInfo -ServerInstance <ServerInstanceName> -SymbolsOnly, I realized that the symbols are missing.
Get-NAVAppInfo Command results

To generate the symbol reference run the command finsql.exe Command=generatesymbolreference, Database="<Database Name>", ServerName=<ServerInsstanceName>

Go to C:\Program Files\Microsoft Dynamics 365 Business Central\140\Service, run CMD Prompt as Administrator and paste the above command

Running finsql.exe Command=generatesymbolreference

This didn't generate the symbols.

To install the System App and Test App as a part of symbols, go to the Product DVD and search for *.app in Folder
Search System.App and Test.App

Now you can use Publish-NAVApp to upload extensions to Business Central

Publish-NAVApp Test App and System App

Now, upon running Get-NAVAppInfo

Get-NAVAppInfo with Test App and System App

Hence, its now time to refer to my old blog Tenant default is not accessible
So, now that only the Application(BaseApp) App is yet to be installed, the steps are as follows.
- Export TXT Objects into a single folder. Exception: Codeunit ID should not be >= 2000000001
Exported TXT Objects in a folder

- Run Generate Symbols:
"Microsoft.Dynamics.Nav.SymbolReferenceGenerator.exe" "C:\Users\cfadmin\Desktop\TXT" "C:\Users\cfadmin\Desktop\" Application 14.0.29530.0

Now the App file is generated, you need to publish using Publish-NAVApp and check with Get-NavAppInfo

PublishNAVApp for BaseApp

Now Restart the Server Instance and download symbols from VS Code.

and upon installation of the extension, the Business Central Environment shows the successful deployment of the extension.


This blog focused on the area where you can migrate your customization with the upgraded database.
Also, the data can be migrated into respected tables using OnInstall and OnUpgrade triggers in AL Development.

Hopefully, this blog helps in installing your AL Language Customization to BC Upgraded Database.


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

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 update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i