FormattingCop on ALCops

Semicolon after method or trigger declaration (FC0001)

Mon, 01 Jan 0001 00:00:00 +0000

Method and trigger declarations should not end with a semicolon. The semicolon is only required after statements, not after procedure or trigger headers.

While the AL compiler accepts a trailing semicolon, it is not idiomatic and reduces code consistency.

Example

The following procedure declaration incorrectly ends with a semicolon:

codeunit 50100 MyCodeunit
{
 procedure MyProcedure(); // Semicolon after method or trigger declaration [FC0001]
 begin
 end;
}

To fix this, remove the semicolon from the declaration:

Casing mismatch (FC0002)

Mon, 01 Jan 0001 00:00:00 +0000

AL is case-insensitive, but consistent casing improves readability and professionalism. When referencing identifiers (variables, procedures, fields, etc.), the casing should match the original declaration.

This rule detects when the casing of a reference differs from its declaration.

A code fix is available for this diagnostic.

Example

The following code has casing mismatches:

codeunit 50100 MyCodeunit
{
 procedure MyProcedure()
 var
 CustomerName: Text;
 begin
 customername := 'Test'; // Casing mismatch [FC0002]
 MYPROCEDURE(); // Casing mismatch [FC0002]
 end;
}

To fix this, use consistent casing that matches the declaration:

Use parenthesis for function calls (FC0003)

Mon, 01 Jan 0001 00:00:00 +0000

Function calls should always include parentheses, even when there are no arguments. This makes it visually clear that a procedure is being invoked rather than a variable being accessed.

Omitting parentheses is allowed by the compiler but reduces code clarity.

A code fix is available for this diagnostic.

Example

The following code calls a function without parentheses:

codeunit 50100 MyCodeunit
{
 procedure MyProcedure()
 begin
 DoSomething; // Use parenthesis for function calls [FC0003]
 end;

 local procedure DoSomething()
 begin
 end;
}

To fix this, add parentheses to the function call: