The action that the consultant should recommend instead of mapping prospects and students’ employers to the standard Account field in Salesforce is A.Populate the employer Affiliation record in the Primary Business Organization field1.This is because EDA uses a different account model than the standard Salesforce account model, which allows for more flexibility and scalability in capturing the complex relationships and affiliations that exist in the education sector2.
In EDA, an Account can represent different types of entities, such as an individual person, a household, an educational institution, an organization, or a course offering. Each Account can have a record type that defines its attributes and behavior. EDA also provides two custom objects, Relationship and Affiliation, that allow for creating connections between Accounts and Contacts. A Relationship is a connection between two Contacts, such as a parent-child or a mentor-mentee relationship.An Affiliation is a connection between a Contact and an Account, such as a student’s enrollment in a course offering, or an employee’s association with an organization2.
By using the Affiliation object, the system admin can link prospects and students to their employers, which are represented by Accounts with the Organization record type. The systemadmin can also specify which Affiliation is the primary one for each Contact, by populating the Primary Business Organization field on the Contact record. This field is a lookup to the Affiliation object, and it allows for displaying the employer’s name and other information on the Contact page layout.By using this approach, the system admin can avoid creating duplicate or unnecessary Accounts, and can leverage the EDA data model to capture the full network of prospects and students1.
B. Select Administrative as the Default Account Model in EDA Settings and C. Select Organization as the Default Account Model in EDA Settings are not valid actions for this scenario. The Default Account Model in EDA Settings is a setting that determines how EDA creates Accounts for new Contacts that are created in Salesforce. The Administrative Account Model creates one Account per Contact, and assigns the same name to both records. The Household Account Model creates one Account per household, and assigns a household name to the Account. The Organization Account Model creates one Account per organization, and assigns an organization name to the Account.However, these settings do not affect how EDA mapsprospects and students’ employers to the standard Account field in Salesforce, as they only apply to new Contacts and Accounts that are created in EDA3.
