A higher education institution has used Salesforce for many years and has Person Accounts enabled. The institution wants to install the Education Data Architecture (EDA) in its existing Salesforce environment.
Which consideration should the consultant discuss with the institution?
A. Person Accounts are unsupported in EDA.
B. A support ticket is required to disable Person Accounts.
C. Person Accounts can only be merged with Administrative Accounts.
A. Person Accounts are unsupported in EDA.
Explanation:
The Education Data Architecture (EDA) is designed primarily to work with the Household Account model, which manages individuals (students, families) as Contacts linked to Household Accounts.
Person Accounts, which combine Account and Contact into a single record, are not supported by EDA because EDA relies heavily on the separation of Accounts and Contacts to represent households and relationships.
Therefore, institutions using Person Accounts face significant challenges when implementing EDA and should carefully consider this limitation.
Why not the others?
B. A support ticket is required to disable Person Accounts.
Person Accounts cannot be disabled once enabled; they are permanent in the org.
C. Person Accounts can only be merged with Administrative Accounts.
This is not accurate; merging Person Accounts with Administrative Accounts is not a standard Salesforce or EDA practice.