Loading

Unable to Report on Field History Tracking of a Detail Object in a Salesforce Master-Detail Relationship

Data pubblicazione: Jul 5, 2026
Descrizione
Salesforce does not support reporting on field history tracking for custom objects that are defined as the detail side of a Master-Detail Relationship.
Why this limitation exists: Existing reports cannot drive sharing from another table. When a custom object is a child of an Account and its sharing visibility is controlled by the parent, the report would need to use the Account's sharing model to determine which history rows to display. This capability has not been implemented in Salesforce.
For example, if a custom object is a child of Account and is defined as a Master-Detail (detail side), field history tracking reports are not available for that object.

To request this, please vote for Report on Field History Tracking for Detail Object in Master-Detail Relationship on the IdeaExchange.

 

Risoluzione

Salesforce does not support field history tracking reports on custom objects defined as the detail side of a Master-Detail Relationship because reports cannot drive sharing from a parent table. The following workarounds provide alternative methods to track field changes in Salesforce.

Workaround Options for Field History Reporting

  1. Create workflows that capture a field's value when the record is saved.
  2. Use Reporting Snapshot to capture data at a point in time. See the limitations in Troubleshoot Reporting Snapshots.
  3. Change the relationship of the custom object from a Master-Detail relationship to a Lookup relationship.

Note: Changing a Master-Detail relationship to a Lookup relationship has implications for sharing, roll-up summary fields, and record deletion. Review Object Relationships Overview before making this change.

 

Numero articolo Knowledge

000384812

 
Caricamento
Salesforce Help | Article