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

A technical upgrade focuses on moving the application and database to Business Central while keeping business logic intact. It prepares the system for functional upgrades and modern AL-based development.
A technical upgrade focuses on moving the application and database to Business Central while keeping business logic intact. It prepares the system for functional upgrades and modern AL-based development.
Begin by installing Business Central using the official setup media provided by Microsoft.
During installation, configure the required environments such as:
This process installs all core components, including the Business Central Server, Web Client, and Development Environment.
Once installation is complete, open the NAV/Business Central Development Environment as an Administrator to ensure you have sufficient permissions for schema and object operations.
When working with Azure SQL, connect using the following naming format:
SQLDatabaseServerName.database.windows.netThis ensures the development environment can correctly locate and authenticate against the Azure SQL application database used by Business Central.
In the Database Information window:
This step links your development tools to the correct Business Central service tier.
Business Central no longer supports direct customization of Codeunit 1.
To proceed:
This replacement acts as a bridge during the upgrade and allows the system to compile successfully.
Next, compile all application objects:
This identifies inconsistencies between the application and database without making immediate schema changes.
After converting a Dynamics NAV 2018 database to Business Central, you will likely encounter compilation errors—even in standard objects.
Common reasons include:
Review each error carefully and fix them before proceeding. This step is critical for a stable upgrade.
If V2 extensions were previously published, they must be repaired.
Use the PowerShell cmdlet:
Repair-NAVAppFor multitenant environments, remount the tenant database after completing the repair to ensure extension metadata is correctly aligned.
Finally, synchronize the tenant database with the application database.
This applies schema changes and aligns metadata between the application and tenant layers.
At this point, the technical upgrade is complete.
While the system is now technically upgraded, several important steps remain before it is fully operational.
Business Central includes newer versions of JavaScript control add-ins.
This ensures UI components work correctly in the modern client.
For single-tenant environments, install the required V2 extensions using:
Install-NAVAppVerify that each extension installs successfully and behaves as expected.
Custom logic previously placed in Codeunit 1 must now be moved into appropriate management codeunits.
This step:
After the upgrade, some pages and reports may no longer appear in search.
To fix this:
This restores usability in the Web Client.
As the final step, upload the customer license file compatible with Business Central.
This enables:
The technical upgrade lays the foundation for:
Completing these steps carefully ensures a stable, supported Business Central environment ready for the next phase of modernization.


START
|
v
Install Business Central
|
v
Open Development Environment (Admin)
|
v
Connect to Application Database
(Azure SQL / On-Prem SQL)
|
v
Connect to Business Central Server Instance
|
v
Import Codeunit 1 Replacement
|
v
Compile All Objects
(Schema Sync Later)
|
v
Fix Compilation Errors
(Standard + Custom Objects)
|
v
Repair Published V2 Extensions
|
v
Synchronize Application & Tenant Databases
|
v
TECHNICAL UPGRADE COMPLETE
|
v
-----------------------------------------
POST-TECHNICAL UPGRADE
-----------------------------------------
|
v
Upgrade JavaScript Control Add-ins
|
v
Install V2 Extensions
|
v
Transition Custom Code
(Codeunit 1 → Management Codeunits)
|
v
Configure Pages & Reports
(Rebuild Search Index)
|
v
Upload Customer License
|
v
READY FOR FUNCTIONAL UPGRADE / AL EXTENSIONS
END
Premanath Kumarage
Author

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.