Skip to main content

msdyn365bc - Preprocessor Directives in AL Introduction.

Hi Readers,

Continuing what's new in business central 2020 wave 2.

In this series, we’ll learn about Preprocessor Directives, available directives in AL, and when, why and how why they are used.

As the name justifies, preprocessor directives are a block of statements that gets processed before the actual compilation starts. AL preprocessor directives are the commands for the compiler that affects the compilation process.

#AL, #msdyn365bc

These commands specifies which sections of the code to compile or how to handle specific errors and warnings.

  • AL preprocessor directive begins with a # (hash) symbol and all preprocessor directives last for one line. 
  • Preprocessor directives are not statements, so they do not end with a semicolon (;).
  • Preprocessor directives are terminated by new line rather than semicolon.

In AL, like in other programming languages, preprocessor directives can be used to make code conditional, to suppress warnings, or to enable expand and collapse in code. 

Preprocessor directives can be divided into the following groups. For more information about each type, use the links provided below - 

Any code can be made conditional, including table fields, and checked using a conditional directive. 

To check code using a conditional directive, you must define a symbol to check. 

A symbol returns a Boolean value; true or false. 

Symbols can be defined at the beginning of a source file and the scope of the specific symbol is the file that it is defined within. 

You can also define symbols in the app.json file, and then the scope is global for the extension.

This is how a code execute with/without preprocessor directives.

In Next article in this series, we will talk about these directives with examples. 

If you have any questions, add as comments to this article.

Regards,
Saurav Dhyani

www.sauravdhyani.com

Comments

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.