Business Central development in AL, built to survive every update
Custom extensions, reports, APIs and integrations written in AL and structured as clean extensions, with source control, tests and deployment pipelines behind them.
The challenge
Modern Business Central does not allow changes to the base application. Everything you add lives in an extension that has to keep working as Microsoft ships monthly updates and two major releases a year. That rewards small, well-scoped extensions built on events, and punishes clever shortcuts.
Technology we use
How we approach it
The same four steps apply whether the project is a rollout, an integration or a fix. Only the depth changes.
Specify
A short technical spec: objects touched, events used, data added, permissions required.
Build in AL
Table and page extensions, codeunits, interfaces and events, following AL conventions and the analyzers (CodeCop, UICop, AppSourceCop, PerTenantExtensionCop).
Test
AL test codeunits for the logic that matters, plus scenario testing in a sandbox with production-like data.
Deploy and observe
Pipelines for build and publish, and Application Insights telemetry so problems are visible after release.
What is included
- Table extensions, page extensions and new pages
- Codeunits, events, interfaces and enums
- Reports and document layouts
- API pages, queries, XMLports and web services
- Approval and workflow extensions
- Permission sets and role centre simplification
- Performance review and optimization
- Source control, build pipelines and deployment
What you get from it
- Extensions that upgrade cleanly instead of blocking updates
- Code your next developer can read and maintain
- Fewer production incidents thanks to tests and telemetry
- Performance considered from the first design
Related pages
Related services
- AL developmentAL extensions, APIs, reports, events, testing and deployment.
- Business Central customizationCustom fields, workflows and logic built as upgrade-safe extensions.
- Business Central API integrationAPI pages, OData, HttpClient calls and OAuth 2.0 authentication.
- Business Central supportIssue resolution, enhancements and update reviews after go-live.
Read more
What Is AL in Business Central? Extensions Explained
AL is the language of Business Central extensions. Here is how objects, extensions and events fit together.
AL Event Subscribers Explained: Extending Business Central Safely
How events let you change Business Central behaviour without touching base code, with examples and pitfalls.
Frequently asked questions
Do you build per-tenant extensions and AppSource apps?
We build per-tenant extensions for client environments. AppSource apps carry additional technical and validation requirements, which we can assess against your plans.
Can you fix or refactor an existing extension?
Yes. We review the code, dependencies and telemetry first, then agree whether to patch, refactor or rewrite.
Do you follow Microsoft's AL guidelines?
Yes. We build on events, avoid base-object modification, and run the code analyzers as part of the build.