Microsoft AL App Extensions

GL Accounts follow a specific lifecycle to allow localization apps to modify account numbers. The process involves registering a base account for the W1 localization and then allowing subsequent localization apps to intercept and modify that account number via an integration event.

The GL Account Lifecycle

1. Initialization: Call AddGLAccountsForLocalization() at the start of your process. This procedure must add the base account for the W1 localization using ContosoGLAccount.AddAccountForLocalization(AccountName, AccountNo). This creates a key-value pair in the temporary table 4769 "Contoso GL Account" (e.g., 'Employees Payable' -> '5850').
2. Interception: Immediately after adding the W1 account, fire the OnAfterAddGLAccountsForLocalization() integration event. This allows localization apps (e.g., a Canada localization app) to call AddAccountForLocalization again with the same AccountName but a different AccountNo (e.g., 'Employees Payable' -> '23850').
3. Resolution: When the application needs the account number, call the descriptive procedure (e.g., EmployeesPayable()). This procedure should use ContosoGLAccount.GetAccountNo(AccountName) to look up the current localized value from the temporary table.

Implementation Example

To implement this pattern, define a descriptive procedure for the account number and a name procedure, and manage the registration in a setup procedure.

// Example implementation of the GL Account pattern

trigger OnRun()
begin
    AddGLAccountsForLocalization();

    // Use the descriptive procedure to get the (potentially localized) account number
    ContosoGLAccount.InsertGLAccount(EmployeesPayable(), EmployeesPayableName(), ...);
end;

local procedure AddGLAccountsForLocalization()
begin
    // 1. Add the base W1 account
    ContosoGLAccount.AddAccountForLocalization(EmployeesPayableName(), '5850');

    // 2. Fire event to allow localization apps to modify the AccountNo
    OnAfterAddGLAccountsForLocalization();
end;

var
    ContosoGLAccount: Codeunit "Contoso GL Account";
    EmployeesPayableLbl: Label 'Employees Payable', MaxLength = 100;

// 3. The consumer calls this to get the localized AccountNo
procedure EmployeesPayable(): Code[20]
begin
    exit(ContosoGLAccount.GetAccountNo(EmployeesPayableName()));
end;

procedure EmployeesPayableName(): Text[100]
begin
    exit(EmployeesPayableLbl);
end;

[IntegrationEvent(false, false)]
local procedure OnAfterAddGLAccountsForLocalization()
begin
end;

Helper codeunits (found in DemoTool/Contoso Helpers/...) simplify inserting demo data by hiding complexity and handling cross-company logic (e.g., W1 vs NA).

Key Features of Helpers:

• Company Type Abstraction: Automatically handles Company Type logic.
• Conflict Management: Use the Exists and OverwriteData variables to control behavior when a record already exists. If OverwriteData is true, the helper will update the existing record instead of throwing an error.

// Example: Inserting a Product Posting Group using a helper
procedure InsertGenProductPostingGroup(ProductGroupCode: Code[20]; Description: Text[100]; DefaultVATProdPostingGroup: Code[20])
var
    ContosoCoffeeDemoDataSetup: Record "Contoso Coffee Demo Data Setup";
    GenProductPostingGroup: Record "Gen. Product Posting Group";
    Exists: Boolean;
begin
    ContosoCoffeeDemoDataSetup.Get();

    if GenProductPostingGroup.Get(ProductGroupCode) then begin
        Exists := true;
        if not OverwriteData then
            exit;
    end;

    GenProductPostingGroup.Validate(Code, ProductGroupCode);
    GenProductPostingGroup.Validate(Description, Description);

    if ContosoCoffeeDemoDataSetup."Company Type" = ContosoCoffeeDemoDataSetup."Company Type"::VAT then
        GenProductPostingGroup.Validate("Def. VAT Prod. Posting Group", DefaultVATProdPostingGroup);

    if Exists then
        GenProductPostingGroup.Modify(true)
    else
        GenProductPostingGroup.Insert(true);
end;

To allow users to configure your module, implement a setup table and a configuration page. Ensure your data generation logic uses the values stored in these configuration tables.

Setup Table Requirements:

• Define fields for configuration (e.g., StartDate).
• Use InherentPermissions for initialization logic.
• Set DataPerCompany = true if configuration is company-specific.

Setup Page Requirements:

• Use PageType = Card.
• Set SourceTable to your setup table.
• Use OnOpenPage to trigger record initialization (e.g., Rec.InitRecord()).

table 5282 "Module Setup"
{
    DataClassification = CustomerContent;
    InherentEntitlements = RMX;
    InherentPermissions = RMX;
    Extensible = false;
    DataPerCompany = true;
    ReplicateData = false;

    fields
    {
        field(1; "Primary Key"; Integer) { DataClassification = SystemMetadata; }
        field(2; StartDate; Date) { Caption = 'Start Date'; }
    }

    keys
    {
        key(Key1; "Primary Key") { Clustered = true; }
    }

    [InherentPermissions(PermissionObjectType::TableData, Database::"Module Setup", 'I')]
    internal procedure InitRecord()
    begin
        if Rec.Get() then
            exit;
        Rec.Insert();
    end;
}

page 5281 "Module Setup"
{
    PageType = Card;
    SourceTable = "Module Setup";
    
    layout
    {
        area(Content)
        {
            group("Setup Data")
            {
                field(StartDate; Rec.StartDate) { }
            }
        }
    }

    trigger OnOpenPage()
    begin
        Rec.InitRecord();
    end;
}

table 5282 "Module Setup"
{
    DataClassification = CustomerContent;
    InherentEntitlements = RMX;
    InherentPermissions = RMX;
    Extensible = false;
    DataPerCompany = true;
    ReplicateData = false;

    fields
    {
        field(1; "Primary Key"; Integer)
        {
            DataClassification = SystemMetadata;
            Caption = 'Primary Key';
        }
        field(2; StartDate; Date)
        {
            Caption = 'Start Date';
            ToolTip = 'Specifies the start date for the scenario.';
        }
    }

    keys
    {
        key(Key1; "Primary Key")
        {
            Clustered = true;
        }
    }

    [InherentPermissions(PermissionObjectType::TableData, Database::"Module Setup", 'I')]
    internal procedure InitRecord()
    begin
        if Rec.Get() then
            exit;

        Rec.Insert();
    end;
}

page 5281 "Module Setup"
{
    PageType = Card;
    Caption = 'Module Setup';
    SourceTable = "Module Setup";
    Extensible = false;
    DeleteAllowed = false;
    InsertAllowed = false;

    layout
    {
        area(Content)
        {
            group("Setup Data")
            {
                field(StartDate; Rec.StartDate) { }
            }
        }
    }

    trigger OnOpenPage()
    begin
        Rec.InitRecord();
    end;
}