Skip to main content

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

Introduction:

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.


Pre-requisites:

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

Demonstration:

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\App.app" 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.

Conclusion:

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.

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

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 Ed...

Installing LS Central - POS on local machine

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan...