Account Object Data Modeling Requirements

Required Mappings and Relationships

Required relationships for Contact Point Email, Contact Point Phone, Contact Point Address, and Party Identifier objects are always Many:1 relationships in the data model because many contact points can belong to one account.

Required relationships for the Account object are always 1:Many relationships in the data model because one account can have multiple contact points.

Object Name	Object API Name	Field Labels	Field API Names	Required Mapping
Account	ssot__Account__dlm	Account Id (primary key) Account Name	ssot__Id__c ssot__Name__c	Account.ID → ContactPointAddress.Party Account.ID → ContactPointApp.Party Account.ID → ContactPointEmail.Party Account.ID → ContactPointPhone.Party Account.ID → PartyIdentificationId.Party
Contact Point Address	ssot__ContactPointAddress__dlm	Contact Point Address Id (primary key) Address Line 1 City Party Postal Code State Province	ssot__Id__c ssot__AddressLine1__c ssot__CityId__c ssot__PartyId__c ssot__PostalCodeId__c ssot__StateProvinceId__c	ContactPointAddress.Party → Account.ID
Contact Point App	ssot__ContactPointApp__dlm	Contact Point App Id (primary key)	ssot__Id__c	ContactPointApp.Party → Account.ID
Contact Point Email	ssot__ContactPointEmail__dlm	Contact Point Email Id (primary key) Party Email Address	ssot__Id__c ssot__PartyId__c ssot__EmailAddress__c	ContactPointEmail.Party → Account.ID
Contact Point Phone	ssot__ContactPointPhone__dlm	Contact Point Phone Id (primary key) Formatted E164 Phone Number Party	ssot__Id__c ssot__FormattedE164PhoneNumber__c ssot__PartyId__c	ContactPointPhone.Party → Account.ID
Party Identification	ssot__PartyIdentification__dlm	Party Identification Id (primary key) Identification Name Identification Number Party Party Identification Type	ssot__Id__c ssot__Name__c ssot__IdentificationNumber__c ssot__PartyId__c ssot__PartyIdentificationTypeId__c	PartyIdentificationId.Party → Account.ID