What's the difference?

The built-in Change Log system is extremely powerful, but without careful configuration it can easily put stress on the system. Because every insert, modification, and deletion is stored as a new record, logging too many fields or tables can cause the Change Log table to grow rapidly, leading to performance issues as it scales.

The overwhelming amount of information can also make it hard to understand and follow.

How is it better?

By giving you greater control over when and how changes are logged, including the ability to ignore non-meaningful updates—such as when a field changes from blank or zero, or changes are reverted.

We also introduce commit-based logging, which treats change logs like database transactions. A log record is created to capture the original and new values, but subsequent changes update the same log entry until it is explicitly committed. This prevents excessive log growth while preserving meaningful change history. Commit operations can be tied to approval workflows or certain events such as when a field's value changes.

In addition, we introduce snapshot logging, allowing you to capture the state of important fields at specific moments—such as when an event occurs—instead of monitoring and logging every incremental change.