It has been a long time coming, we have all been warned, a wave of obsolete Business Central Object deletes is happening with Business Central 2025 Wave 1, aka Release 26. This is important housekeeping, but if you have been ignoring the warnings on some older code, it is time to address the code-based elephant in the room.

This is important for the longevity of Business Cental. As the platform grows and new processes replace old ones, we need to trim the system back. It doesn’t make it less painful for those of us that have used those objects.

Quick note to the new developers out there, when we refer to an “object” we are talking about the things we can create in Business Central AL. These are Tables, Pages, Enums, Code Units, all that stuff.

You can find a list of all the objects that are about to be deleted here: Deleted objects in the Base App and first-party apps – Business Central | Microsoft Learn

We are going to go back a little and look at what the warning signs are of an impending object delete. What does it look like when an object is obsoleted?

Note the orange underline of a warning. The details in the Problems panel. There is also a handy reason and recommendation listed there, Thanks BC Development Team!

If we drill into the field definition it looks like this:

When the time comes for this field to be removed, that obsolete state flag changes to removed, and the code will look like this:

At this point, if you have a current set of dependencies, this code will not compile. You will be forced to remove the references to that object. In the case of this example field, swap the description field for the Message field.

So, the big question; I’ve used objects that are going to be removed, what happens to my existing, already deployed extensions?

Well, you are required to update the Extension to remove the objects and transfer that functionality to supported objects then deploy an update. This may take a little research on your end, depending on the objects used and the quality of the recommendations provided by the BC team.

If you have been running Continuous Integrations and Next Major testing, you should have plenty of warning. If not, you may get this warning in your email, if you are configured as a notification recipient in the Business Central Admin Center.

If you don’t update the extension, updates to that system will fail. If you wait too long the extension will be removed.

There are cases where you want to deploy an update, but you don’t want to implement that change in the current release. There is an option to release your update along with the Business Central updates.

In Extension Manager, during the upload process you can opt to have the extension deployed with the Next Minor or Next Major version update.

When selecting this option, your current extension is not update, but instead the update is queued. When the next Business Central update is run the new extension is automatically installed.

Now, if you want to get ahead of the game, here are things that are obsoleted in BC 25: Obsoletions for 25.0. VS Code and AL Go CI/Next Major testing should be identifying these fields and flagging them as a warning. These will eventually be removed so you might want to get started on them as well.

This is just part of life working with a SaaS platform. Keeping up with the Business Central development team can be a challenge at times. The good news is that we typically have a lot of notice of breaking changes. You’ve got this!

Microsoft has published some additional details here: Essential Clean-Up Guide for Partners: 2025 Release Wave 1 – Microsoft Dynamics 365 Blog