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

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

Background processing in Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central serves the same purpose—running tasks without user interaction—but the architecture and execution model are fundamentally different.
Understanding this difference is critical during NAV → Business Central upgrades.
JOBQUEUEGUIALLOWED())| Aspect | NAV NAS | Business Central Job Queue |
|---|---|---|
| Execution Model | Separate Windows Service | Built-in Server Component |
| Deployment | Manual | Automatic |
| UI Handling | GUIALLOWED() required | Not applicable |
| Architecture | C/AL, classic | AL, extension-based |
| Cloud Support | ❌ Not supported | ✅ Native |
| Scalability | Limited | High |
| Monitoring | Basic logs | Advanced telemetry |
| Upgrade Complexity | High | Low |
| SaaS Compatibility | ❌ | ✅ |
Job Queue Entry
↓
Job Queue Setup (Active?)
↓
NAS Service (JOBQUEUE)
↓
Execute Report / Codeunit
↓
Job Queue Log EntryJob Queue Entry
↓
Job Queue Dispatcher
↓
Background Session
↓
Execute AL Codeunit
↓
Telemetry & LogsNAV NAS
Business Central
👉 This shift removes the need for:
When upgrading from NAV to Business Central:
This is one of the most important technical transitions in a NAV → Business Central upgrade.
| NAV Pattern | Business Central Equivalent |
|---|---|
| NAS Service | Job Queue Dispatcher |
| GUIALLOWED() | Background Session |
| Codeunit 1 logic | AL Management Codeunits |
| Manual scheduling | Platform-managed scheduling |
While both systems solve the same problem—background processing—they belong to entirely different architectural eras.
Understanding this difference helps avoid bad upgrade decisions and ensures a clean, future-proof Business Central solution.

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.

Business Central SaaS Extension from Scratch (Repo-backed, Azure DevOps)
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.