Posts

Writing Your First Business Central API from Scratch (AL Tutorial)

Sooner or later every Business Central developer needs to expose data to the outside world — a website, a Power Automate flow, a mobile app, or another system. The modern way to do this is with a custom API page in AL. Unlike the older "publish as web service" approach, an API page gives you a clean, versioned, high-performance REST endpoint that follows Microsoft's OData v4 conventions. Note: If want to Check Standard API then visit Standard API List   In this tutorial we will build a simple Customer Rating API from scratch, publish it, and call it. You only need VS Code with the AL extension and a Business Central sandbox. Step 1: The table we will expose We will use a small custom table so the example is self-contained. table 50100 "Customer Rating" { DataClassification = CustomerContent; fields { field(1; "No."; Code[20]) { } field(2; "Customer No."; Code[20]) { TableRelation = Cus...

10 Most Common AL Compiler Errors in Business Central ( and How to Fix them)

Every AL developer meets the same handful of compiler errors over and over — usually the moment they hit F5 and the build fails. This post collects the ten you are most likely to see in Visual Studio Code when building Business Central extensions, explains what each one actually means, and shows the fix with a short example. Tip: in VS Code, the error code (like AL0432 ) appears in the Problems panel. Searching that exact code is the fastest way to a fix — so each error below is labelled with its code. 1. AL0185 — The name does not exist in the current context The compiler cannot find a variable, method, or object with that name. Almost always a typo, a missing var declaration, or a dependency you forgot to add to app.json . // Error: 'Custmer' does not exist in the current context Custmer.FindFirst(); // typo // Fix: declare it and spell it correctly var Customer: Record Customer; begin Customer.FindFirst(); end; 2. AL0432 — This method is only support...