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...

If you learned C/AL in the Dynamics NAV era, the good news is that most of your knowledge still applies. AL , the language of Microsoft Dynamics 365 Business Central, kept the core concepts — tables, pages, codeunits, triggers but modernized the syntax and moved everything to an extension-based model. C/AL and the classic C/SIDE environment were retired back in Business Central version 15 (2019), and as of 2026 we are already 13 major versions into the fully AL-based world. This cheat sheet maps the most common C/AL patterns to their AL equivalents so you can migrate old code (or old skills) quickly. 1. The big picture: what changed Concept C/AL (NAV) AL (Business Central) Development tool C/SIDE (Object Designer) Visual Studio Code + AL Language extension Customization model Modify base objects directly Extensions only never modify the base app Object files Stored in the database Plain-text .al files in a project, version-controlled with Git Deployment Import .fob / .txt ...