EDA Triggers

Trigger 1

• TargetX’s “Lead Source Prevention” trigger helps prevent duplicate contact records. It merges duplicate contact records by retaining contact data from the most recently created record and retaining the “Lead Source” field from the original/first record. 
• When a contact record is associated with an account, TargetX’s HEDA Toolkit creates an Affiliation record between the contact and the Account.
• EDA’s “CON_CannotDelete_TDTM” trigger prevents users from deleting contacts that have Affiliation records. 
• When the triggers are turned on, EDA’s “CON_CannotDelete_TDTM” triggers prevents users from deleting the duplicate contact record. (Cannot de-dupe records).

Trigger 2 

• If you are using TargetX’s HEDA Toolkit v1.0, please review the following. 
• TargetX’s Application Requirements Manager (ARM) trigger has a @future method that calls a @future method in TargetX’s HEDA Toolkit trigger vXXX. When both triggers are turned on, ARM will create additional Enrollment History records as Checklist items (TargetX HEDA Toolkit v 1.0).
• TargetX’s “Protect From Deletion” checkbox on Account record and its related trigger prevents users from deleting any account marked ‘protected’ and prevents any edits to the Account record. 
• EDA’s “ACCT_IndividualAccounts_TDTM” trigger updates a field on the Account any time a contact is created for it. 

Required Steps for EDA Compatibility