Field Change Log

Who changed this credit limit?

Odoo can answer that for the handful of fields its own developers marked as tracked, and for nothing else.

Every audit-log module for Odoo answers it by recording everything — and every one of them ends up unusable for the same reason. The day somebody actually has to answer the question, the log has four million rows in it and no way to find the one that matters.

Who, when, on which record, what it was and what it became — for the fields you named and nothing else.

Nothing is recorded until it is named here. Choosing is the feature.

Written for whoever reads it a year later

Values are stored as they read on the screen, not as they sit in the database: a linked record by its name, a selection by its label. A stored key like invoice means nothing to somebody reading the log after the fact.

The record's name is kept as it read at the time, so an entry still means something after the record is renamed — or deleted.

What it refuses to record

A write that sets a field to the value it already holds. That is not a change, and a log full of them is the log nobody reads.

Anything written while a module is installing or updating — thousands of rows in one go, and not one of them a decision anybody made.

Its own tables, and Odoo's internal plumbing.