Small and medium business | Business Central, N...

Business Central Migration from Version 25 to 27 On-Premises – Application Version Management

(7) Share

Report

Posted on by CK-14110819-0

Hello everyone,

We are currently working on upgrading Business Central from version 25 to version 27 On-Premises.

We have noticed that the procedure to update the "Application Version" has changed:
-Task 15 “Change Application Version,” which was still present in the upgrade to BC26, has disappeared in BC27.
-The “-ApplicationVersion” parameter has been removed from the Set-NAVApplication cmdlet (the applicationversion field also no longer exists in the $ndo$dbproperty table):
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-unmodified-application-to-v27

This is mentioned in the following link, but without additional details:
https://learn.microsoft.com/en-us/powershell/business-central/cmdlets-changes?view=businesscentral-ps-27

(Note: The Get-NAVApplication cmdlet still returns the "ApplicationVersion" field in its output but empty)

We previously used the ApplicationVersion field to perform version checks. Which data can we now rely on to ensure that a database has indeed been upgraded to BC27? Only the SolutionVersionExtension field?

Thank you in advance for your help.

Best regards,

Categories:

Dynamics 365 Business Central migration

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Jainam M. Kothari 15,627 Super User 2025 Season 2 on at

Like (4)

Report

Hello,

Microsoft recommends using the SolutionVersionExtension (typically set to the Base Application extension) and verifying the platform version (should be 27.x.x.x) along with the Base Application extension version from the Installed Extensions table or via AL/PowerShell.

https://yzhums.com/24344/

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 5,078 on at

Like (1)

Report

Hello,

BC 27 removed the ApplicationVersion field completely, so you can’t use it anymore to verify upgrade state.

To check whether a database is truly upgraded to BC 27, Microsoft now expects you to rely on:

1. Extension versions (System Application + Base Application must be 27.x).

2. solutionversionextension in $ndo$dbproperty (this replaces the old ApplicationVersion concept).

Those two values together are now the correct way to confirm a BC27 upgrade.

Regards,

Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,309 Super User 2025 Season 2 on at

Like (0)

Report

Hi, hope the following can give you some hints.

Considerations before upgrading to Business Central version 26 and later - Business Central | Microsoft Learn

Thanks.

ZHU

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,078 Most Valuable Professional on at

Like (0)

Report

Hi, good day
I hope this can help you, and give you some hints. Upgrading Microsoft System and Base Application to Version 27 - Business Central | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,147 on at

Like (1)

Report

Hi,

Hi,

The ApplicationVersion concept was removed in BC27. You can no longer rely on that field or the old cmdlet parameter. For version checks, use:

SolutionVersionExtension (reflects the installed application version).
Alternatively, check the platform version via Get-NAVServerInstance or the application version from the installed extensions list (System Application and Base Application).

These are now the official indicators that the database is upgraded to BC27.

Thanks

Rishabh

Was this reply helpful? Yes No