Change tracking
See exactly what changed in your Salesforce schema, and when.
Change tracking records the history of your schema so you always know what changed, when, and — where possible — who changed it. It runs automatically from the moment you connect an org.
Here's what a single recorded change looks like:
How changes are detected
Every sync diffs the live schema against the stored snapshot and records a change event for each added, modified, or removed object, field, or attribute.
Each event captures the old and new values for what changed:
Something new appeared in your schema — a new object, field, or attribute.
An existing attribute changed — for example, a field's label or type.
Something that existed in the snapshot is no longer present.
Old and new are schema values, never records
The old and new values on a change event are schema attribute values — such as a field's prior label or its previous type — never record data. SchemaForce never reads what's stored in your fields.
The Changes timeline
Browse the Changes timeline to see events in order. You can filter to focus on what matters:
- By object — narrow to changes on a specific object.
- By change type — show only additions, modifications, or removals.
Because each object's dictionary page has a Change history tab, you can move between the org-wide timeline and a single object's history without losing the thread.
Attribution
Where Salesforce's Setup Audit Trail has a matching entry, a change is attributed to who made it. If there's no matching entry, the change is still recorded — just without an attributed actor.
Why some changes have no attributed actor
Attribution depends on a matching entry in Salesforce's Setup Audit Trail. Not every schema change has a corresponding audit-trail entry to match against, so some changes are recorded without an actor. The change itself is never lost — only the "who" may be unavailable.
History starts when you connect
History can't be backfilled
Change history starts the day you connect your org and can't be reconstructed retroactively. SchemaForce can only track changes that happen after your baseline snapshot is built.
The longer SchemaForce runs, the more complete your history becomes — it's the core, compounding value of the product. The sooner you connect an org, the more history you'll have to look back on.