Critical Changes in Business Central 2025: Removal of Obsolete Objects in Version 26

Summary of Changes in Business Central 2025 (Version 26)

Microsoft has announced a series of significant changes to Dynamics 365 Business Central with the arrival of version 26, scheduled for 2025. This update marks a turning point in the evolution of the platform, as it involves the permanent removal of numerous obsolete objects and functionalities, which will have a direct impact on customized solutions built on previous versions.

Removed Elements and Technical Scope

What is being removed in version 26?

With the goal of optimizing performance, simplifying the architecture, and encouraging the use of modern extensions, Microsoft has decided to remove:

Tables marked as obsolete

Approximately 150 tables that had been marked as obsolete in previous versions.

Fields outside the active data model

More than 1,000 fields that are no longer part of the active data model.

Procedures and system objects that have been replaced

Various procedures, triggers, and system objects that have been replaced by new, more efficient APIs or functionalities.

These elements have been part of the system for years, but they are no longer aligned with Microsoft’s recommended best practices for AL development and event‑based extensions.

Impact by Roles and Scenarios

Who is affected?

This change primarily affects:

• Developers who have created custom extensions using obsolete objects.
• Companies that maintain vertical solutions or specific customizations built on earlier versions of Business Central.
• Technical partners who manage hybrid environments or migrations from on‑premises versions.

Update Risks and Recommendations

Potential Risks When Upgrading to Version 26

The removal of these objects may lead to:

• Compilation errors in extensions that reference removed tables or fields.
• Functional failures in automated processes that relied on obsolete logic.
• Operational disruptions if a prior review is not carried out before upgrading to version 26.

Key Recommendations for a Safe Transition

Key recommendations:

1. Comprehensive technical audit: Review all custom extensions to identify dependencies on objects marked as obsolete.
2. Use of analysis tools: Use the Obsolete Tag Analyzer and CodeCop to detect references to deprecated elements.
3. Migration plan: Establish a roadmap to adapt your solutions to the new structures and available APIs.
4. Training and documentation: Ensure that the development team is aware of Microsoft’s latest guidelines for AL extensions.

Notable Examples of Removed Tables and Fields

Examples of Removed Tables and Fields

1. VAT Amount Line – Completely removed.
2. Job Queue Entry (ID 472)
   • Removed fields: On Hold Due to Inactivity, Timeout (sec.), Error Message 2–4, Priority.
3. Job Queue Log Entry (ID 474)
   • Removed fields: Processed by User ID, Error Message 2–4.
4. Notification Entry (ID 1511)
   • Removed fields: Error Message 2–4.
5. Sales Invoice Line (ID 113)
   • Removed fields: Cross-Reference No., Unit of Measure (Cross Ref.), Cross-Reference Type, Cross-Reference Type No., Product Group Code.
6. Purchase Line (ID 39)
   • Removed fields: same as in Sales Invoice Line.
7. Customer (ID 18)
   • Removed fields: Picture, Tax Area Display Name, Id.
8. Vendor (ID 23)
   • Removed fields: Picture, Id.
9. Sales & Receivables Setup (ID 311)
   • Removed fields: Insert Std. Sales Lines Mode, Insert Std. Lines on Quotes, Insert Std. Lines on Orders, Insert Std. Lines on Invoices, Insert Std. Lines on Cr. Memos.
10. Purchases & Payables Setup (ID 312)
    • Removed fields: same as in Sales & Receivables Setup.
11. CRM Integration Record (ID 5331)
    • Removed field: Option Mapping Failure.
12. Power BI Report Configuration / Buffer / Uploads (IDs 6301, 6302, 6307)
    • Removed field: EmbedUrl.
13. Image Analysis Setup (ID 2020)
    • Removed fields: Period start date, Number of calls, Limit value, Limit type.
14. Service Shipment Line / Invoice Line / Cr.Memo Line / Service Line
    • Removed field: Product Group Code.
15. Sales Header / Invoice Header / Cr.Memo Header / Line Archive
    • Removed fields: Payment Instructions, Sell-to Customer Template Code, Bill-to Customer Template Code, Id.
16. Item (ID 27)
    • Removed fields: Product Group Code, Id.
17. Item Ledger Entry (ID 32)
    • Removed fields: Cross-Reference No., Product Group Code.
18. Transfer Shipment Line / Receipt Line / Transfer Line
    • Removed field: Product Group Code.

Detection of impacts on your customizations

How to identify whether your customizations are affected? You can use the following tools and strategies:

• Obsolete Tag Analyzer: To detect references to obsolete objects.
• Preprocessor Symbol CLEANSCHEMA: To anticipate removals.
• Table 2000000041 “Field”: Filter by ObsoleteState = Removed to see which fields are marked for removal.

Conclusion and next steps

The release of Business Central version 26 represents a solid step toward a cleaner, more modern platform aligned with Microsoft’s cloud‑first approach. However, for companies with legacy customizations, this transition requires careful planning and a thorough technical review.

Adapting to these changes will not only prevent operational issues but also allow you to take better advantage of the platform’s new capabilities.

ABD Consulting and IT Solutions: support during the upgrade to Business Central 2025 (version 26)

At ABD Consulting, we help audit AL extensions, detect obsolete dependencies, and plan the migration to version 26 without impacts on daily operations.

Do you want to review your environment before upgrading? Contact ABD and prepare your move to Business Central 2025 safely.