Skip to main content

How to upgrade Microsoft Dynamics NAV C/AL Objects to Microsoft Dynamics Business Central AL Objects

Introduction:

When migrating from NAV 2017 to NAV 2018 i.e moving from C/AL to AL the created objects need not be created again from scratch in AL. This blog demonstrates how we can create the AL objects from C/AL using Txt2Al in Command Prompt.

Pre-requisite:

  1. NAV 2018.
  2. Backup of Objects in TEXT or FOB format.

Steps:

1. Import objects in NAV 2018 from the created  .TXT or .FOB files.

In NAV Development Environment goto,

Files > Import > Choose the .FOB or  .TXT file > Replace all the objects

2. Export the objects in New Syntax to .TXT files.

  • Create a directory to store the objects in .TXT format which will be exported as new syntax. Here, ‘source’ is the name of the directory used.
    Use  ‘mkdir source ‘
  • Create a directory to store the .AL that will be created by TXT2AL Converter utility. Here ‘target’ is the name of the directory used.
    Use ‘mkdir target’
  • To export the objects in .TXT format in NewSyntax use the following command

    where Source Directory = ‘source’
    Filename = ‘CU0-5.txt’
    Database Name = ‘Demo Database NAV (11-0)’
    SQL Server Instance = ‘.\NAVDEMO’
    Type of Object = ‘codeunit’
    ID = ‘50000..50005’  —-is the ID range

    Similarly, for
    Tables: 
    Type of Object = ‘table’; ID=’50000..50005′;filename=’TAB0-5.txt’
    Pages: 
    Type of Object = ‘page’; ID=’50000..50005′;filename=’PAG0-5.txt’
    Queries:
    Type of Object = ‘query’; ID=’50000..50005′;filename=’Query0-5.txt’
    Reports:
    Type of Object = ‘report’; ID=’50000..50005′;filename=’REP0-5.txt’
    Menusuite:
    Type of Object = ‘menusuite’; ID=’50000..50005′;filename=’MS.txt’
    XMLPort:
    Type of Object = ‘xmlport’; ID=’50000..50008′;filename=’XMLPort.txt’
    NOTE: TXT2AL requires objects exported in New Syntax


3. Generate the .AL object files using the  TXT2AL converter.

To generate the .AL file from the .TXT files from source folder, run the following command

where Source Directory = ‘source’
Target Directory = ‘target’
–rename = Used to create new .AL file per new object and give it the appropriate name of the ID and name.

Conclusion:

Thus, in this way, we can convert the objects in C/AL to AL format. Although the conversion is not 100% perfect but, most of the redundant work can be avoided.

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