Field History Tracking allows you to select the fields you want to track. Whenever a user modifies any of the fields selected below, the old and new field values are added to the History related list as well as the date, time, nature of the change, and user making the change. Note that multi-select picklist and large text field values are tracked as edited; their old and new field values are not recorded.
The field history data is retained for up to 18 months. It is possible to track the field history of custom objects and the following standard objects.
Contract line items
Modifying any of these fields adds an entry to the History related list. All entries include the date, time, nature of the change, and who made the change.
Consider the following when working with field history tracking:
- Changes to fields with more than 255 characters are tracked as edited, and their old and new values are not recorded.
- Tracked field values are not automatically translated; they display in the language in which they were made. For example, if a field is changed from Green to Verde, Verde is displayed no matter what a user’s language is, unless the field value has been translated into other languages via the Translation Workbench. This also applies to record types and picklist values.
- Changes to custom field labels that have been translated via the Translation Workbench are shown in the locale of the user viewing the History related list. For example, if a custom field label isRed and translated into Spanish as Rojo, then a user with a Spanish locale sees the custom field label as Rojo. Otherwise, the user sees the custom field label as Red.
- Changes to date fields, number fields, and standard fields are shown in the locale of the user viewing the History related list. For example, a date change to August 5, 2012 shows as 8/5/2012 for a user with the English (United States) locale, and as 5/8/2012 for a user with the English (United Kingdom) locale.
- If a trigger causes a change on an object the current user doesn’t have permission to edit, that change is not tracked because field history honors the permissions of the current user.
- Track Field History for Standard Objects
You can enable field history tracking for standard objects in the object’s management settings.
- Track Field History for Custom Objects
You can enable field history tracking for custom objects in the object’s management settings.
- Disable Field History Tracking
You can turn off field history tracking from the object’s management settings.
- Field Audit Trail
Field Audit Trail lets you define a policy to retain archived field history data up to ten years, independent of field history tracking. This feature helps you comply with industry regulations related to audit capability and data retention.
“Explore – Techila Global Services, A Salesforce development company”