Skip to main content
Brian Makas (N/A) a posé une question dans #Data Management
Due to the limit of 20 fields that can be tracked on an Account we sometimes have to add/remove fields from tracking based on special projects and/or evolving needs.

 

Is there any way to see an audit log of when individual field tracking is turned on/off other than the following options?

 

  1. adding custom code to track more efficiently (not worth expense)
  2. relying on documentation maintained outside of SFDC (mistakes can be made)
  3. looking at setup audit trail (very close but  only goes back 6 months unless this is manually exported & deduped before 6 months go by )
  4. simply looking at the first/last changes tracked for any given field (doesn't account for gaps or situations when field is rarely changed)
1 réponse
  1. 23 sept., 14:45

    Hi Brian,

    Unfortunately, the standard Field History Tracking feature doesn't maintain a separate, permanent audit history showing when each individual field was enabled or disabled for tracking.

    The Setup Audit Trail is the main standard place to identify configuration changes, but as you mentioned, its retention is limited. Exporting it periodically is one way to retain that history longer.

    If you need a permanent audit of tracking configuration changes, you'd generally need to maintain it outside the standard Field History Tracking mechanism—for example, by periodically exporting the Setup Audit Trail or using a custom/configuration-management process.

    Looking at the first and last history records for a field won't reliably identify gaps, so I wouldn't recommend that as an audit method. 

0/9000