web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Update BC 25.5 to BC 26.0 Failed

(2) ShareShare
ReportReport
Posted on by 10
Hello,
I am getting following error when updating from BC 25.5 to BC 26.0 (SaaS), please help! Thank you.
---------
Your update failed with the following error. Resolve this error before attempting to update again.
Message: Microsoft extension 'Base Application' version 26.0.30643.34581 by 'Microsoft' failed to synchronize the database schema. Table 17 G/L Entry :: The field 'Src. Curr. Non-Ded. VAT Amount' cannot be located. Removing fields is not allowed. NST Tenant Detailed State: The extension 'Base Application by Microsoft 26.0.30643.34581' has a newer version than the current schema version '25.5.30849.34576'. For OnPrem users, run Sync-NavApp to update the schema. For SaaS users, please contact your Microsoft Partner. The extension 'Application by Microsoft 26.0.30643.32695' has a newer version than the current schema version '25.5.30849.31230'. For OnPrem users, run Sync-NavApp to update the schema. For SaaS users, please contact your Microsoft Partner. The extension 'Email - Outlook REST API by Microsoft 26.0.30643.32695' has a newer version than the current schema version '25.5.30849.31230'. For OnPrem users, run Sync-NavApp to update the schema. For SaaS users, please contact your Microsoft Partner. ...
---------
Sources:
 
 
 
I have the same question (0)
  • Sohail Ahmed Profile Picture
    11,177 Super User 2026 Season 1 on at

    Root Cause: Field 'Src. Curr. Non-Ded. VAT Amount' was removed from G/L Entry table in BC 26.0, but your database still references it.





       
    •  


















    •  
  • Verified answer
    Valentin Castravet Profile Picture
    32,710 Super User 2026 Season 1 on at

    First, ignore the message below, it’s clearly AI generated and incorrect.

    Second, this appears to be a Microsoft bug. All environments seem to be failing to upgrade due to this error. I’d wait for an update from Microsoft, there’s a thread about it on Yammer - Viva Engage : Dynamics 365 Business Central Partner Community (Formerly: Development) : View Conversation

     

    Valentin Castravet
    Work: Zander ERP Services
    Blog: Dynamics 365 Business Central Insights
    LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,382 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,625 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,376

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans