- (+91) 9112-041-412
- support@stw-services.com
Business Central Customization & AL Development Services
Extensions that fit your processes and keep working through every Microsoft update.
When Microsoft Dynamics 365 Business Central doesn’t handle a process the way your business needs, STW Services’ Business Central developers design and build AL extensions that close the gap: new fields and pages, business rules, documents and reports, workflows, APIs and integrations, without touching Microsoft’s code.
- Configure-first advice
- Upgrade-safe extensions
- Source code & docs handed over
pageextension 50100 "Customer Card Ext" extends "Customer Card" { layout { addafter("Credit Limit (LCY)") { field("Credit Check Required"; Rec."Credit Check Required") { ApplicationArea = All; ToolTip = 'Requires approval before release.'; } } } } // Business logic via events; Microsoft's code untouched [EventSubscriber(ObjectType::Codeunit, Codeunit::"Release Sales Document", 'OnBeforeReleaseSalesDoc', '', false, false)]
When standard Business Central isn’t quite enough
Business Central covers a lot out of the box, but most growing companies eventually hit something it doesn’t do their way. Each of these can be solved with a well-designed AL extension, if it’s genuinely needed and built to last.
- A pricing, discount or commission rule standard price lists can’t express
- Mandatory data on customers, items or documents: compliance fields, certificates, batch attributes
- Documents that must follow a customer’s or regulator’s format
- An approval or validation step before posting
- A repetitive manual task: imports, recalculations, document creation
- An external system needing data the standard APIs don’t expose
- Old NAV customizations to rebuild before moving online
Extensions, not code changes
In Dynamics NAV, customizations often meant editing Microsoft’s code, which turned every upgrade into a project. Business Central customizations are extensions written in Microsoft’s AL language in Visual Studio Code.
- Extensions add tables, fields, pages, reports and logic
- They extend standard objects with table, page and report extensions
- They react to events published by the base application
- Microsoft’s code is never modified; on Business Central online it can’t be
Microsoft ships two major releases a year plus monthly updates. Well-built extensions carry on working.
Business Central AL development, end to end
Table & page extensions
New fields, FactBoxes, actions and views on customers, items and documents; whole new pages for your own data.
Custom business logic
Validation, calculated fields, pricing logic, automatic document creation, via event subscribers and codeunits.
Reports & layouts
Custom reports and report extensions; Word, Excel and RDLC layouts for invoices, statements and more.
Workflows & approvals
New workflow events and responses, combined with Power Automate approvals in Outlook or Teams.
Custom APIs
API pages and queries exposing exactly the data an external system needs, versioned and permissioned.
Business events
Custom events that let Power Automate or other systems react when something important happens.
Imports & job queue
Scheduled imports and processing with error handling and logging.
Role Centers & UX
Role-specific home pages, cues and simplified pages that cut clicks.
Permissions
Permission sets for every new object, so access stays controlled.
Configure, automate, install or develop?
Every extension adds testing to each Microsoft update, so we check the alternatives first and tell you which one wins.
Standard features
The requirement matches a setup, workflow or layout option.
Power Automate
The gap is a hand-off, approval or notification, not core logic.
Marketplace app
A maintained app on Microsoft Marketplace already solves it.
AL extension
The requirement is specific to your business and must live in Business Central.
How we deliver an AL extension
Understand
Walk through the process; define “done”, including edge cases.
Design
Objects, events, data changes, permissions, upgrade impact.
Estimate
Fixed scope for defined work, or time-based for evolving needs.
Develop
In a sandbox, in Git, with Microsoft’s AL analyzers.
Test
Developer tests plus UAT by your key users.
Deploy & hand over
Release notes, documentation and source code.
Practices that protect your upgrades
Customizations are only upgrade-safe if they’re engineered that way. These practices are standard on every extension we build.
- Event-driven design, never copied standard code
- CodeCop, UICop, PerTenantExtensionCop (AppSourceCop for Marketplace apps)
- Git source control: reviewable, reversible changes
- Sandbox first, including Microsoft preview versions
- Upgrade & install codeunits for clean version installs
- Performance-aware queries; heavy work on the job queue
- Documentation any qualified developer can follow
Typical customization requests
Examples of the work, not client case studies.
- Mandatory compliance fields and validation
- Automatic POs from approved sales orders
- Customer-specific invoice and delivery-note layouts
- Commission calculation and salesperson reporting
- Project extensions: cost categories, retention fields
- Batch, quality or certificate attributes
- Scheduled imports of price lists, bank files or orders
- API endpoints for portals, e-commerce or logistics
AL development questions
What buyers ask before commissioning Business Central customization.
Ask us a questionWhat is AL in Business Central?
AL is Microsoft’s programming language for Business Central. Customizations are written in AL as extensions in Visual Studio Code and deployed to Business Central environments.
Will customizations break when Microsoft updates Business Central?
Extensions built on events and extension objects are designed to survive updates. Microsoft announces deprecations in advance, and we test against new versions in a sandbox.
What’s the difference between personalization, configuration and customization?
Personalization is what users do themselves; configuration uses built-in setup with no code; customization means developing an AL extension. We check the first two before recommending the third.
Can you take over extensions another partner built?
Yes, with the source code. We review quality and compatibility and propose a plan.
How much does a customization cost?
It depends on the objects affected, the logic, integrations and testing. Small changes take hours; larger extensions are scoped as projects.
Should we customize at all?
Only when it pays off. We’ll tell you when configuration, Power Automate or an existing app would do the job with less long-term cost.
Have a requirement standard Business Central doesn’t cover?
Describe the process and what isn’t working. We’ll tell you whether it needs code, and if it does, the simplest maintainable way to build it.
- A reply from someone who knows Business Central
- Practical next steps, whether or not we work together
- No obligation
Book a Business Central Consultation
Tell us about your Business Central requirement. We’ll reply with practical next steps.
- Pick “Business Central Solutions” in the form
- Share your current system and what you need
- Or email support@stw-services.com