
Business Central SaaS Extension Design: Implementing Plant Tracking with AL Event Subscribers
In many manufacturing and service-oriented organizations, sales transactions need to be associated with a Plant (or operational unit).

Here’s a battle-tested, simple structure for one repo hosting many Business Central extensions, plus a clean naming/ID/range/versioning standard that won’t hurt you later when you add CI/CD.
Here’s a battle-tested, simple structure for one repo hosting many Business Central extensions, plus a clean naming/ID/range/versioning standard that won’t hurt you later when you add CI/CD.
Recommended repo structure (one repo, many apps)
Option A (recommended): One folder per extension under /apps
Works great with pipelines later, easy to clone anywhere.
bc-extensions/
README.md
.gitignore
.editorconfig (optional)
.azure-pipelines/ (later)
apps/
CustomerExt-01/
src/ (AL project lives here)
app.json
.vscode/
launch.json
settings.json
HelloWorld.al (or your objects)
tables/
pageextensions/
codeunits/
docs/ (optional: specs)
overview.md
test/ (optional: test app later)
VendorExt-01/
src/
app.json
.vscode/...
...
tools/ (optional)
scripts/
Why this is best
Option B: Monorepo with shared “workspace” and common VS Code config
Only do this if your team is mature with AL tooling; otherwise it adds complexity.
VS Code launch.json strategy for multi-app repo
You have two clean choices:
Choice 1 (simplest): each app has its own .vscode/launch.json
Choice 2 (more advanced): one shared .vscode at repo root
Naming standards
Repo name
App folder name
Use: PascalCase + short suffix:
app.json name
Match folder:
app.json publisher
Use one publisher consistently (important later for upgrades):
Avoid “Default Publisher” once you start real work.
App IDs (GUIDs)
Rule
Practical approach
Tip: Keep a small registry in /README.md or /docs/apps.md listing:
Example:
| App | App ID | Range |
| CustomerExt-01 | xxxxxxxx-xxxx-... | 50100–50149 |
Object range strategy (IDs)
You need a clean plan so multiple apps never collide.
Option A (simple and scalable): allocate blocks per app
Example allocation (easy to remember):
This works well if you keep apps small.
Option B (more enterprise): allocate blocks per domain
Then each app inside the domain takes a smaller block.
Recommendation for you
Since you’re building multiple discrete extensions: Option A (block per app) is the cleanest.
Versioning standard (app.json version)
Use Semantic-ish versioning
MAJOR.MINOR.PATCH.BUILD
Examples:
Practical rule (easy to follow)
Runtime / platform / application fields
Keep runtime aligned with your BC version
If your SaaS is current (v25/26/27 etc), typical runtime is 13+, 14+, 15+, 16+, 17+ depending on the environment.
Rule:
Recommended approach
Git branching / workflow (simple but correct)
Branches
Commit message standard
Tagging (later)
When you release a version:
.gitignore for multi-app repo
At repo root:
# AL generated artifacts (in any app)
**/.alpackages/
**/.alcache/
**/.snapshots/
**/*.app
# VS Code - keep only shared config if you want
**/.vscode/*
!**/.vscode/launch.json
!**/.vscode/settings.json
# OS
.DS_Store
Thumbs.db
“Open the right folder” rule (avoids confusion)
When working on an app:
✅ Open folder:
Not the repo root, not /apps, not src of another app.
Suggested “starter template” per app (clean folders)
Inside each src:
src/
app.json
.vscode/
launch.json
settings.json
tableextensions/
pageextensions/
codeunits/
permissionsets/
profiles/ (optional)

Premanath Kumarage
Author

In many manufacturing and service-oriented organizations, sales transactions need to be associated with a Plant (or operational unit).

Business Central SaaS Extension from Scratch (Repo-backed, Azure DevOps)

Below is a clear, side-by-side comparison of NAV NAS vs Business Central Job Queue, written in plain language, plus a visual flow diagram you can embed in your blog. This is ideal for developers and consultants transitioning from NAV to Business Central.
Start here
A working session, not a sales call. Bring the process your current system fights you on, and we will tell you plainly what it would take to fix it.
Newsletter
Stay ahead with Microsoft Business Applications.
Insights, implementation advice and practical ideas to help your business get more from Microsoft technology.
By subscribing, you acknowledge MicroCloud 360’s Privacy Policy.