EDA and TargetX compatibility Overview

Overview

TargetX is focused on ensuring that our clients (new and existing) can combine the full benefits of TargetX products with the advantages of HEDA. To ensure institutions can take advantage of HEDA with minimal effort, TargetX introduced the TargetX HEDA Toolkit. This software package mirrors like-data between the TargetX and HEDA data models. This allows institutions to take advantage of HEDA without completing data migration or extensively updating existing workflows and data import processes.

The TargetX Recruitment CRM contains objects similar to those in Salesforce’s Higher Education Data Architecture (HEDA). To be compatible with HEDA, we have created data mirroring triggers. These triggers allow institutions to mirror data across “like” objects, between the Recruitment CRM and HEDA, within the same Salesforce Org.

Since most of the TargetX products use custom objects included in the Recruitment CRM, this data mirroring is needed if you use the HEDA “like” objects.

The table below lists the objects that are included in the data mirroring:

TargetX Recruitment CRM	HEDA
Enrollment History	* Affiliations
Relationships	Relationships

*Note: The Affiliations object is used for any Contact to Account relationship in HEDA, not just for previously attended institutions. This means that Enrollment History will be a subset of Affiliations. We will cover how to only mirror specific Affiliation records with the Enrollment History object later in this document.

All TargetX products offer full compatibility using both TargetX and HEDA objects, with a few exceptions noted in the Known Limitations article. Institutions should utilize TargetX fields/objects with HEDA. This will allow the institution to use TargetX’s ongoing product upgrades/development and standard import processes.

Application Review Tool and EDA

TargetX Decision can read file attachments such as transcripts and recommendations attached to the Account, Contact, and Enrollment History objects. Attachments on other objects cannot be pulled into the Decision review tool. The TargetX HEDA Toolkit mirrors only data and not file attachments between the Enrollment History and Affiliations object.

For institutions utilizing TargetX Decision, please attach files that need to be reviewed on the Account, Contact, and Enrollment History objects.

EDA Contact Fields

There are currently eight EDA fields on the Contact object that duplicate existing TargetX Contact object fields.

Required Steps for EDA Compatibility:

Institutions should utilize the TargetX Contact fields.
TargetX requires that institutions install and turn on a trigger in TargetX’s EDA Toolkit to mirror the data between the following fields in the Contact record. This will have no impact on data storage.
- TargetX’s Alt Email field = EDA’s Alternate Email field
- TargetX’s Birth Country field = EDA’s Country of Origin field
  - Please note the TargetX “Birth Country” field being mapped is a text field. Update the picklist options to include all values mapped.
- TargetX’s IPEDS Hispanic field = EDA’s Ethnicity field
  - Please note the EDA Ethnicity field specifies whether the Contact is Hispanic or Latino.
- TargetX’s Gender field = EDA’s Gender field
- TargetX’s Mailing Address Type field = EDA’s Primary Address Type field
- TargetX’s IPEDS Ethnicities field = EDA’s Race field
  - Please note the picklist options do not match. Update the picklist options to include the same values.
- TargetX’s Religion field = EDA’s Religion field
  - Please note the picklist values do not match. Update the picklist options to include the same values.
- TargetX’s SSN field = EDA’s Social Security Number field
  - Please note that EDA’s Social Security Number is an encrypted field; the TargetX SSN field is not encrypted.
Institutions already utilizing Salesforce and TargetX should review the General EDA Guidance for Existing Salesforce and TargetX Institutions section for additional steps.

EDA Multiple Addresses

"EDA lets [your institution] track multiple addresses for Contacts and Accounts you create. This is useful if Contacts or Accounts have seasonal addresses, work addresses, home addresses, or other addresses you'd like to keep track of for mailings." TargetX products and standard file imports by default, write into the standard Salesforce address fields on the contact and account objects. EDA has the ability to create new address records whenever new addresses are saved in the standard Salesforce address fields. For more information about how multiple address work in EDA, please review EDA: Add or Update Addresses*.

Required Steps for EDA Compatibility:

Institutions should take advantage of EDA's multiple address functionality if it would benefit the institution. TargetX products will continue writing to the standard Salesforce address fields and use EDA's ability to create new address records.

*https://help.salesforce.com/s/articl...EDA.htm&type=5

EDA Relationship

TargetX’s Relationship object (part of TargetX Base package) tracks contact-to-contact, contact-to-account, & account-to-account connections. EDA’s Relationship object tracks contact-to-contact connections.

Required Steps for EDA Compatibility

Institutions should utilize the TargetX Relationship object.
Institutions should install TargetX’s HEDA Toolkit and turn on the settings to mirror data bi-directionally between TargetX’s Relationship object and EDA’s Relationship object. Please see How to implement the TargetX HEDA Toolkit for detailed instructions.
Institutions can select which Relationship records they want to mirror between the TargetX Relationship object and EDA’s Relationship object.
Mirroring this data will have an impact on data storage. Please utilize TargetX HEDA Storage Calculator to estimate the implications for your institution.
Institutions already utilizing Salesforce and/or TargetX should review the General EDA Guidance for Existing Salesforce and/or TargetX Institutions article for additional steps.

Standard Import Files and EDA

TargetX currently supports standard file imports (e.g., SAT, GRE) written to TargetX objects and not EDA objects.

Required Steps for EDA Compatibility

Institutions should install TargetX's HEDA Toolkit and turn on the settings to mirror data bi-directionally between TargetX's and EDA's like-objects.
For institutions looking to write directly into EDA objects, please note that the standard file imports will need to be updated by your institution to write into EDA objects.

TargetX Enrollment History and EDA Affiliation

TargetX’s Enrollment History object tracks high schools, colleges/universities, and academic programs a student has attended. EDA tracks similar information within the Affiliation object.

Required Steps for EDA Compatibility

Institutions should utilize the TargetX Enrollment History object.
Institutions should install TargetX’s EDA Toolkit and turn on the settings to mirror data bi-directionally between TargetX’s Enrollment History object and EDA’s Affiliation object. Please see: How to implement the TargetX HEDA Toolkit for detailed instructions.
- Institutions can select which Affiliation records they want to mirror between the TargetX Enrollment History object and EDA’s Affiliation object.
- Mirroring this data will have an impact on data storage. Please utilize TargetX EDA Storage Calculator to estimate the implications for your institution.
Institutions already utilizing Salesforce and/or TargetX that should review the General EDA Guidance for Existing Salesforce and/or TargetX Institutions section for additional steps.

General EDA Guidance for Existing Salesforce and/or TargetX Institutions

Institutions already utilizing Salesforce and TargetX looking to install EDA should review the following areas for potential adjustments and changes to your CRM. Data models are foundational to software. To take advantage of EDA, there may be a need to migrate data, adjust reports, revise form mappings and data integrations, and update administrative and data processes. Whether these areas apply to your institution depends on how your Salesforce org is set up.

Required Steps for EDA Compatibility

Test EDA in a sandbox environment first.
Test EDA against all customizations in your Salesforce org beyond the standard TargetX CRM implementation.
Identify and migrate existing data to like-EDA fields/objects.
Set up new Record Types for Accounts for use in Affiliations.
Update User Profiles to ensure access to appropriate Account Record Types and appropriate fields in other objects.
Update existing or create new Page Layouts to reflect the appropriate fields.
Update existing or create new List Views to reflect the appropriate fields.
Update existing or create new Custom Reports to reflect the appropriate fields.
Update existing or create new import/export tasks to reflect the appropriate fields.
Review and ensure 3rd party products are written to the appropriate fields.

Steps required for TargetX-EDA Compatibility

Higher Ed Institutions New to Salesforce

For institutions utilizing Salesforce for the first time, install EDA in your Salesforce org and utilize the TargetX HEDA Toolkit from the beginning. This will ensure that relevant data is stored in the appropriate EDA objects and can be used and reported seamlessly. This includes the full use of EDA’s Administrative Accounts.

Higher Ed Institutions Already Utilizing Salesforce

For institutions utilizing TargetX that are interested in installing and using EDA, please review the following articles: