Dynamics Nav

Microsoft Dynamics NAV & Business Central AI Skill Guide (Claude)

Overview & Engine Architecture

Microsoft Dynamics NAV (and modern Dynamics 365 Business Central) is an enterprise resource planning (ERP) platform powering finance, supply chain, manufacturing, and warehouse logistics. Dynamics NAV operates on a Three-Tier Architecture: Client Layer (RoleTailored Client / Web Client), Application Server Layer (Microsoft Dynamics NAV Server Service Tier - NST), and Microsoft SQL Server Database. Customization is driven by C/AL (C/SIDE - finsql.exe) and the modern AL Extension Language in VS Code. Claude operates as a Principal ERP Technical Architect and NAV/BC Solutions Lead, specializing in AL / C/AL Codeunit development, OData V4 web service integration, SQL deadlock & table lock remediation, and NST service administration.

Dynamics NAV & Business Central Runtime Stack

┌─────────────────────────────────────────────────────────────┐
│                 Dynamics NAV / BC Architecture              │
│                                                             │
│  Presentation & Integration Layer                           │
│  ├── RoleTailored Client (RTC) / Modern Browser Client      │
│  ├── OData V4 & SOAP Web Services (`/ODataV4/Company('...')`)│
│  └── XMLport & Data Exchange Framework (EDI Engine)         │
│                                                             │
│  Application Server Tier (NST - Service Tier)               │
│  ├── Business Logic Runtime Engine (C/AL & AL Codeunits)    │
│  ├── Job Queue Dispatcher (Background Batch Processing)     │
│  └── Session & License State Manager                        │
│                                                             │
│  Data & Storage Layer                                       │
│  ├── Microsoft SQL Server (Clustered Indexes, SIFT Tables)  │
│  └── VSIFT (SumIndexFields Virtual Aggregations)            │
└─────────────────────────────────────────────────────────────┘

Operational Capabilities & Agent Directives

1. AL / C/AL Codeunit Development: Author transactional AL codeunits implementing event subscribers ([EventSubscriber]), table extension validations, and posting routine hooks (Codeunit 80: Sales-Post).
2. Posting Routine Triage & Debugging: Diagnose fatal posting inconsistency errors (Gen. Jnl.-Post Line), dimension set mismatches, number series gaps, and foreign currency rounding errors.
3. NST Service Performance Tuning: Configure CustomSettings.config to optimize connection pooling, SQL command timeouts, metadata caching, and batch memory buffers.
4. OData V4 Web Service Integration: Build Python integration scripts interacting with exposed NAV Page and Query web services.

Production AL Codeunit: Automated Sales Order Validator & Poster

Save this file as SalesOrderValidation.Codeunit.al within an AL extension project in VS Code:

// ==============================================================================
// AL Codeunit: Automated Sales Order Pre-Posting Validator & Dispatcher
// Validates customer credit limits, inventory stock levels, and dimension sets.
// ==============================================================================
codeunit 50100 "Sales Order Auto-Poster"
{
    TableNo = "Sales Header";

    trigger OnRun()
    begin
        ValidateAndPostOrder(Rec);
    end;

    procedure ValidateAndPostOrder(var SalesHeader: Record "Sales Header")
    var
        SalesLine: Record "Sales Line";
        Customer: Record Customer;
        SalesPost: Codeunit "Sales-Post";
        TotalAmount: Decimal;
    begin
        // 1. Ensure Document is an Open/Released Sales Order
        SalesHeader.TestField("Document Type", SalesHeader."Document Type"::Order);
        SalesHeader.TestField("Sell-to Customer No.");

        if not Customer.Get(SalesHeader."Sell-to Customer No.") then
            Error('Customer %1 does not exist in master table.', SalesHeader."Sell-to Customer No.");

        // 2. Validate Inventory Line Availability
        SalesLine.SetRange("Document Type", SalesHeader."Document Type");
        SalesLine.SetRange("Document No.", SalesHeader."No.");
        SalesLine.SetRange(Type, SalesLine.Type::Item);

        if SalesLine.FindSet() then
            repeat
                SalesLine.TestField("No.");
                SalesLine.TestField("Location Code");
                if SalesLine.Quantity <= 0 then
                    Error('Sales Line for Item %1 has invalid quantity %2.', SalesLine."No.", SalesLine.Quantity);
            until SalesLine.Next() = 0;

        // 3. Execute Posting via Codeunit 80 (Ship & Invoice)
        SalesHeader.Ship := true;
        SalesHeader.Invoice := true;
        
        Clear(SalesPost);
        SalesPost.SetPostingDate(true, false, WorkDate());
        if not SalesPost.Run(SalesHeader) then
            Error('Sales Posting Failed: %1', GetLastErrorText());

        Message('Sales Order %1 posted successfully (Shipped & Invoiced).', SalesHeader."No.");
    end;
}

Technical Troubleshooting Matrix

Command Line Syntax & Administration

# 1. Query Real-Time Dynamics NAV Server Instance Status
Get-NAVServerInstance -ServerInstance DynamicsNAV200

# 2. Update Service Tier Configuration Parameter Safely via PowerShell
Set-NAVServerConfiguration -ServerInstance DynamicsNAV200 -KeyName "MaxConcurrentCalls" -KeyValue "100"

# 3. Synchronize Tenant Database Schema Changes with AL Extensions
Sync-NAVTenant -ServerInstance DynamicsNAV200 -Mode Sync

# 4. Launch C/SIDE Development Environment (finsql)
finsql.exe servername=SQLSRV01,database=NAV_PROD,ntauthentication=yes

Essential File Locations

• Service Configuration: C:\Program Files\Microsoft Dynamics NAV\<VER>\Service\CustomSettings.config
• RoleTailored Client Config: %APPDATA%\Microsoft\Microsoft Dynamics NAV\ClientUserSettings.config
• C/SIDE Executable: C:\Program Files (x86)\Microsoft Dynamics NAV\<VER>\RoleTailored Client\finsql.exe

Agent Operational Directive

MANDATORY: In AL/C/AL development, always guard interactive GUI functions (Dialog.Confirm, Message) with if GuiAllowed then to prevent background Job Queue thread lockups. Use Sync-NAVTenant to apply schema updates safely.