Understanding Limitations to the TargetX-EDA Compatibility

Objects such as Course and Term in EDA look similar to the Course and Academic Period objects in Retention. However, EDA’s objects are dependent on the Account object, and TargetX objects are dependent on the Contact.
If we mirror the data in these objects, we would have to create additional records, such as Account records. This would mean we would be making assumptions about the types of records we create. This could create data integrity issues.

Apex does not allow us to update the ID value involved in the Master-Detail relationship.
For example, if a user creates an Enrollment History record associated with the Jeff Marcum Contact record, an Affiliations record will be created and associated with the same Jeff Marcum Contact record. If the user then updates the same Enrollment History record and changes the Contact to John Smith, we cannot change the Affiliations record to do the same.

To avoid trigger looping, we are not supporting the creation of the reciprocal relationship in EDA.
If the reciprocal relationship record is updated in the future, the record will be mirrored in the TargetX Recruitment CRM.

TargetX’s Retention solution currently has three objects that are similar to objects in EDA.:
- TargetX’s Course object = EDA’s Course object
- TargetX’s Academic Period object = EDA’s Term object
- TargetX’s Academic Profile object = EDA’s Course Connection object
EDA’s objects are dependent on the Account object, and TargetX objects are dependent on the Contact.
The TargetX HEDA Toolkit currently does not mirror data between these objects.
- To mirror the data in these objects, we must make assumptions about creating new records, such as Account records. This could create data integrity issues.

TargetX plans to fully incorporate the EDA course-related objects into the TargetX Retention solution in the near term. Institutions should use the TargetX Retention solution to utilize the TargetX course-related objects.