Cascade Delete Property

Here is another good one. Tip for Cascade Delete Property on New Link Definitions and believe me its very useful. Here it goes

- The property should be set to “Delete”, if the child record has no other relationships through other links. This happens often when using a _XM table for the child BusComp. Without the parent record, the child _XM record is not necessary and should be deleted.
- Set the value to “Clear”, if the link defines a 1:M relationship, but the value could be related to another record through another link (e.g. an activity record, which can be associated to a contact as well as to an account).
Ensure that the FK reference on the activity record is cleared, indicating that there is no longer an account associated to the activity before deleting the related account. the activity should not be deleted, as it still has a relationship to a valid contact.
- The property should be left as “None”, if the link uses an intersection table (M:M).
- Set the Inter Child Delete propert to “TRUE” for a M:M link as long as a child intersection record should be deleted when a parent record is deleted.