Dynamics 365 Business Central: Change Log Management event changes.

I think that everyone of you know that Dynamics 365 Business Central has a built-in Change Log functionality that permits you to track all direct modifications a user makes to data in the database and this is an important feature for auditing requirements (just remember that tracking changes can affect performance, which can cost you time, and increase the size of your database, which might cost you money).

The Change Log functionality is mainly managed in the Change Log Management codeunit, that contains also events for interacting with the change log itself.

In this codeunit, there are the following procedures:

• procedure GetDatabaseTableTriggerSetup(TableID: Integer; var LogInsert: Boolean; var LogModify: Boolean; var LogDelete: Boolean; var LogRename: Boolean)
• procedure IsLogActive(TableNumber: Integer; FieldNumber: Integer; TypeOfChange: Option Insertion,Modification,Deletion): Boolean

and these two procedures until Dynamics 365 Business Central version 25.2 had some integration event raised:

I’ve recently discovered that some partners added their business logic or customizations by subscribing those two events. If you’ve one of those partners, be careful…

What changes now?

Starting from Dynamics 365 Business Central version 25.3 (that should be released in the next hours), Microsoft removed the previously mentioned integration events.

The reason for an immediate removal of those events is mainly related to security. Those events were now so well designed from the beginning, because subscribing to those events permits you to change the log entries or skipping / disabling the log entries for a table. And this is considered a security issue (and I honestly agree).

This event removal can be an immediate breaking change for every partner that used those events for their customizations, so be prepared ton refactor your code before upgrading to version 25.3.

Why Microsoft has not obsolete the event following the standard obsoletion pattern for breaking changes?

Because when Microsoft discovers a security breach, this pattern is not respected (remember this)! When a problem in Dynamics 365 Business Central is related to security, the fix is immediately applied despite being breaking.

Original Post https://demiliani.com/2025/01/21/dynamics-365-business-central-change-log-management-event-changes/