Field History Tracking
- You
can select certain fields to track and display the field history in the
History related list of an object.
- Field
history data is retained for up to 18 months through your org and up to 24
months via the API.
- Field
history tracking data doesn’t count against your Salesforce org’s data
storage limits.
For example:
- AccountHistory represents the history of changes to
the values of an Account record’s fields.
- MyCustomObject__History tracks field history for the
MyCustomObject__c custom object.
General
Considerations
- Salesforce starts tracking field history from the date and time that you enable it on a field. Changes made before this date and time aren’t included and didn’t create an entry in the History related list.
- Use Data Loader or the
queryAll()API to retrieve field history that‘s 18–24 months old. - The Field History Tracking timestamp is precise to a second in time. In other words, if two users update the same tracked field on the same record in the same second, both updates have the same timestamp. Salesforce can’t guarantee the commit order of these changes to the database. As a result, the display values can look out of order.
Field Audit Trail
- Field Audit Trail lets you define a policy to retain archived field
history data up to 10 years from the time the data was archived.
- Field history tracking data and Field Audit Trail data don’t count
against your Salesforce org’s data storage limits.
- Field history is copied from the History-related list into
the FieldHistoryArchive big
object.
- With Field
Audit Trail, you can track up to 60 fields per object. Without it, you can track only 20 fields per object
The following fields can’t be
tracked.
- Formula, roll-up summary, or auto-number
fields
- Created By and Last Modified By
- Expected Revenue field on opportunities
- Master Solution Title or the Master Solution
Details fields on solutions
- Long text fields
- Multi-select fields
