Considerations for Working with Cross-Object Field History

Consider these points when you work with Cross-Object Field History.

• Enable the Field History Tracking to use the Cross-Object Field History in your Salesforce org.
• Field History Tracking supports up to 20 fields per object. With the Field Audit Trail (FAT) add-on, this can be increased to 60 fields. If you need to track more than 60 fields, request approval from Salesforce to track up to 100 fields per object.
• The Cross-Object Field History Lightning web component shows up to 200 records. To narrow down the results, modify the filter criteria.
• You can’t track changes to:
  • Formula, rollup summary, or autonumbered fields
  • Created By and Last Modified By fields
  • Fields that have the AI Prediction checkbox selected
  • Expected Revenue field on opportunities
• For updates to multiselect picklist and large text field values, select the fields under Track changes only.
• Field history tracking supports custom objects in managed packages. However, if the package developer updates the package field history settings, Salesforce doesn’t update those settings during package upgrades.
• If both the new and old values of the Created field are blank, it means the record is being created for the first time.
• You can add up to 5 child nodes for each parent node.
• Field History tracking doesn't track the new values of fields added during the creation of a new record. Hence, Cross-Object Field History doesn't track these changes.
• History records are retrieved based on the date range specified by the user, with a default range of three months.
• The object filter operates in conjunction with the date filter. It doesn't function independently.
• The parent records are retrieved first, followed by the child object records. For example, if the parent record exceeds the threshold limit of 200 records, sometimes the child records ‌won’t retrieved. The threshold is reduced based on the payload time for optimal performance.
• For optimal performance, create graphs using the following recommendations:
  • Max Nested Depth Level: 4 (This is the maximum number of nested vertical objects)
  • Max Child Nodes Per Level: 5 (This is the maximum number of horizontal child objects)
  • Total Records: 200 or less.