“What to Do if the Lookup Record Is Deleted?” Options Are Not Available on a Custom Lookup Field

This article explains why the "What to do if the lookup record is deleted?" options do not appear when you configure a self-referential custom lookup field in Salesforce, and what behavior Salesforce applies instead.

Why the Lookup Deletion Options Are Missing on a Self-Referential Lookup Field

This behavior is by design. When a lookup field references the same object, Salesforce removes the deletion behavior options for the following reasons:

• Removing the options prevents cascade deletion risks.
• In complex relationships, such as circular references, allowing record deletion could unintentionally delete multiple related records.

Example of a Cascade Deletion Risk in a Circular Lookup Relationship

Consider the following circular relationship between records in the same object:

• Record A → Record B → Record C → Record A
• If cascade delete were allowed, deleting one record could delete the entire chain.

Default Behavior When the Referenced Record Is Deleted

To prevent cascade deletion, Salesforce enforces a default behavior. The lookup field value is automatically cleared when the referenced record is deleted. No additional configuration is available for this type of lookup relationship.