Business Central Information sharing: Essential Clean-Up Guide for Partners (Deleted objects in 2025 release wave 1)

Hi, Readers.
I would like to share a piece of information today, Essential Clean-Up Guide for Partners (Deleted objects in 2025 release wave 1).

Microsoft is doing some housekeeping in Business Central, and will introduce a significant change in April with 2025 release wave 1 (v26). The tables and fields in this article have been in the Obsolete::Removed state for more than one major release, and will be permanently deleted. This sweeping clean-up will affect the Base Application and all first-party apps. Over 150 tables have been removed to optimize and clean up the application code.

To ensure a smooth transition, Microsoft will adopt a clean-up cycle every fifth major release. This article describes what you need to know about these changes and how to prepare your applications.

PS:
1. ObsoleteState Property: To obsolete objects, the ObsoleteState Property and ObsoleteTag Property are used to specify where and when an object is marked as obsolete

2. Microsoft Timeline for Deprecating Code in Business Central

3. These tables and fields can also be filtered out in table 2000000041 “Field”.

On Saturday, Japan time, Microsoft also released the following blog:
Essential Clean-Up Guide for Partners: 2025 Release Wave 1 – Microsoft Dynamics 365 Blog

The Dynamics 365 Business Central Release Wave 1 clean-up means that all tables, table extensions, and table fields remaining in the Obsolete::Removed state for more than one major release will be permanently deleted. This sweeping clean-up affects the Base Application as well as all other first-party apps. Already, the removal of over 150 tables has optimized and cleaned up the application code.

And has sent a notification in the BC Yammer Group.

As part of this release, we will remove deprecated tables and table fields in first party Business Central applications for the first time.

For more details and background, please refer to Microsoft’s blog. But please note, for partners, the following must be dealt with.
What should developers do?
If your app references objects in the Obsolete::Removed state then you need to:

Refactor your code: Replace or remove references to these objects before April 2025.
Check upgrade code: Ensure that upgrade code doesn’t rely on removed tables, table extensions or table fields.
Monitor preprocessor symbols: Use the CLEANSCHEMA symbol to anticipate removal timelines.

Microsoft will host two Office Hour calls for partners to join for questions about this process and next steps:

Option 1: February 13, 4:00–5:00PM CET / 7:00-8:00AM PT. Please register here

Option 2: February 18, 8:00–9:00AM CET / 3:00-4:00PM SST. Please register here

PS:
1. Deleted objects in the Base App and first-party apps – Business Central | Microsoft Learn

2. Update Lifecycle for Tenant Customizations – Business Central | Microsoft Learn

3. Maintain AppSource apps and per-tenant extensions – Business Central | Microsoft Learn

4. Business Central 2024 wave 2 (BC25): Manage environment updates more flexibly – Major update: 30(60) days -> 5-month and Optional minor updates

END

Hope this will help.

Thanks for reading.

ZHU