// bitta apps · services
AL Development
Custom AL extensions, AppSource submissions, integrations, performance tuning, and rescue projects for Business Central — built to Microsoft's AL guidelines.
When standard Business Central doesn't fit the way your business runs, AL development closes the gap. Senior AL developers lead every engagement — building custom extensions, integrating Business Central with external systems, tuning slow reports and posting routines, and stepping in on stalled or inherited extension projects. We build to AppSource validation requirements — code reviews, AppSourceCop compliance, and the submission process are part of the engagement.
What can AL development cover?
Custom extensions
Table extensions, page extensions, new pages and reports, event subscribers, and background jobs — packaged as AppSource-ready AL apps.
Integrations
REST/OData APIs, webhooks, Power Platform connectors, Azure Service Bus, and event-driven patterns against Business Central.
Performance tuning
SIFT and index analysis, slow report remediation, posting routine profiling, and telemetry instrumentation.
Rescue projects
Inherited AL codebases, failing upgrades, broken AppSource submissions — we diagnose and rebuild only what's needed. If a previous partner handed your project to a bench, we're the recovery path: the team that scopes your work is the team that delivers it.
Upgrade migrations
C/AL to AL conversion and version-to-version upgrades with regression test plans.
Code reviews
Structured reviews of your AL codebase against Microsoft's AL guidelines and AppSource requirements.
How we work
- 01
Scoping call
We review requirements, existing code, and constraints.
- 02
Proposal
Fixed-scope statement with milestones and acceptance criteria.
- 03
Build & test
Iterative delivery with UAT environments per milestone.
- 04
Package & deploy
AppSource submission or tenant deployment per your preference.
Frequently asked
Can you work inside our existing AL codebase?+
Yes. We work on customer and partner repos, follow your branching/PR conventions, and leave clean, reviewable commits.
Do you sign NDAs?+
Yes. Mutual NDA on request before any code or tenant access is shared.
Do you do AppSource submissions?+
Yes — validation, marketing copy alignment, and iteration through Microsoft review.
Will our extensions keep working when Microsoft updates Business Central?+
That's the point of building them as AL extensions: they sit alongside the base application instead of modifying it, so Microsoft's twice-yearly release waves don't overwrite your code. We build to AppSource-grade standards even for private extensions and use preview environments to catch breaking changes before they reach production. AL extension upgrade strategies →
How is AL development work priced?+
Fixed scope, fixed price. After a scoping call you get a written proposal within five business days covering milestones, acceptance criteria, and one number — no open-ended time-and-materials drift. Larger builds are split into milestones, each with its own acceptance criteria and UAT pass. How our pricing works →