Guidelines for Using Cascade Delete
Be careful. If set incorrectly, the Cascade Delete property might cause data integrity problems or orphaned records.
If you use the Cascade Delete property, then use the following guidelines:
Cascade Delete is not available for a many-to-many link. A child might be the child of more than one parent when Siebel CRM uses a many-to-many link, so Siebel CRM deletes the intersection record but leaves the child record intact.
If you delete a record that a foreign key of another table references, then Siebel CRM might or might not delete the reference to the record. If it does not delete the reference, then row IDs might reference records that do not exist. If used with a multi-value group, then Siebel CRM might convert the foreign key to display No Match Row Id.
The link applies to parent child relationships. Siebel CRM treats a one-to-one extension table as an extension of the parent, so it keeps the extension table synchronized with the parent.
Use a link except for a one to many extension table that involves two different business components.
To involve grandchild records, use the Deep Delete business component user property. For more information, see Siebel Developer's Reference.