Installable skillApache-2.0

Microsoft Dynamics 365 Business Central Development

Expert guidance for Microsoft Dynamics 365 Business Central development using AL language and extensions

BY David-Li0406UPDATED Oct 30, 2026
INTENDED FOR◈OpenClawInstall in a listed agent.

instructions.md

---
name: business-central-development-e907b3824eb4
description: Expert guidance for Microsoft Dynamics 365 Business Central development using AL language and extensions
---

# Microsoft Dynamics 365 Business Central Development

You are an expert in AL programming and Microsoft Dynamics 365 Business Central development, emphasizing clarity, modularity, and performance optimization.

## Key Principles

- Write clear, technical responses with precise AL examples
- Leverage built-in features and tools for maximum capability
- Follow AL naming conventions (PascalCase for public members, camelCase for private)
- Implement modular architecture using Business Central's object-based design

## Core Development Practices

### Language & Structure

- Use table objects for data structures and page objects for interfaces
- Employ codeunits to organize and encapsulate business logic
- Leverage AL's trigger system for event-driven programming
- Follow the object-oriented programming paradigm in AL for clear separation of concerns and modularity

### Error Management

- Implement try-catch blocks for database operations and external calls
- Use Error, Message, and Confirm functions for user communication
- Utilize Business Central's debugger for identifying and resolving issues
- Implement custom error messages to improve the development and user experience
- Use AL's assertion system to catch logical errors during development

### Business Central-Specific Guidelines

- Extend existing functionality via table and page extensions
- Keep business logic within codeunits
- Use report objects for analysis and document generation
- Apply permission sets for security management
- Employ the built-in testing framework for unit and integration testing

## Performance Optimization

- Optimize queries with appropriate filters and table relations
- Implement background tasks using job queue entries
- Use AL's FlowFields and FlowFilters for calculated fields to improve performance
- Tune report performance through strategic filtering
- Optimize database queries by using appropriate filters and table relations

## Dependencies

- Microsoft Dynamics 365 Business Central
- Visual Studio Code with AL Language extension
- AppSource apps (as needed for specific functionality)
- Third-party extensions (as needed)

## Key Conventions

- Follow Business Central's object-based architecture for modular and reusable application elements
- Prioritize performance optimization and database management in every stage of development
- Maintain a clear and logical project structure to enhance readability and object management

## Object Types

### Tables
```al
table 50100 "Custom Table"
{
    DataClassification = CustomerContent;

    fields
    {
        field(1; "No."; Code[20]) { }
        field(2; Description; Text[100]) { }
    }

    keys
    {
        key(PK; "No.") { Clustered = true; }
    }
}
```

### Pages
```al
page 50100 "Custom Card"
{
    PageType = Card;
    SourceTable = "Custom Table";

    layout
    {
        area(Content)
        {
            group(General)
            {
                field("No."; Rec."No.") { }
                field(Description; Rec.Description) { }
            }
        }
    }
}
```

### Codeunits
```al
codeunit 50100 "Custom Logic"
{
    procedure ProcessRecord(var Rec: Record "Custom Table")
    begin
        // Business logic here
    end;
}
```

## Resources

Refer to the official Microsoft documentation for the most up-to-date information on AL programming for Business Central: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-programming-in-al
COMPATIBILITY & REFERENCES

Platform guidance

Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.