Is it a known issue that field history tracking doesn't detect changes to a lookup field as the result of the parent object being deleted?


We had a big data integrity issue and was able to track it down a parent object being deleted. For example, CustomObject_c.Account_c, can get cleared if the related account is deleted, but it's not showing up in the history tracking. I've reviewed the tracking field history considerations in the help docs and it doesn't mention this limitation anywhere. Hoping to find out if this is expected behavior before I go down the long road of filing a bug ticket with Salesforce.


I belive this is answer you are looking for:

If the parent record in a lookup relationship is deleted, the field history tracking for 
the child record does not record the deletion. For example, if a parent account is deleted, 
enter preformatted text here`the Account History related list for the child account does not show the deletion.
  • from documentation :)
  • Here's the link: help.salesforce.com/… – jkraybill Mar 14 '14 at 6:23
  • Nah, I knew I forgot something :) – Artur Kępczyński Mar 14 '14 at 7:30
  • @ArturKępczyński thanks for the link, was surprised to find out that there is now an option for cascade deletes with regular lookup fields (it requires contacting sfdc support to enable). – Ralph Callaway Mar 15 '14 at 23:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.