Table: Contact
Columns
NameTypeConstraintsDescription
contact_KEYintNOT NULLAssigned by COMMON_dp_Allocate_Unique_Identifiers. Database assigned primary key for this table.
update__staff_KEYintNOT NULL
update_date_utcdatetimeNOT NULL
namenvarchar (250)NOT NULLName of the contact.
companynvarchar (250)NOT NULLCompany of the contact.
titlenvarchar (250)NOT NULLTitle of the contact.
salutationnvarchar (40)NOT NULLSalutation for opening letters.
urlnvarchar (2048)NOT NULLWebsite address.
phone_positionnvarchar (14)NOT NULLSemicolon seperated list of contact_phone_type_KEY values indicating the user's preferred order of phone numbers.
address_positionnvarchar (4)NOT NULLSemicolon seperated list of contact_address_type_KEY values indicating the user's preferred order of displaying addresses.
email_positionnvarchar (6)NOT NULLSemicolon seperated list of contact_email_type_KEY values indicating the user's preferred order of displaying e-mail addresses.
primary__contact_phone_type_KEYintNOT NULLIndicates which phone type is the primary phone number.
primary__contact_address_type_KEYintNOT NULLIndicates which address type is the primary address.
mailing__contact_address_type_KEYintNOT NULLIndicates which address type is the mailing address.
contact_type_KEYintNOT NULLKey to Contact Type.
file_asnvarchar (250)NOT NULLName as it appears in Outlook's "File as"
create_date_utcdatetimeNOT NULL
contact_guiduniqueidentifierNOT NULL
primary__contact_email_type_KEYintNOT NULLIndicates which email type is the primary email.
create__changeset_KEYintNOT NULL
update__changeset_KEYintNOT NULL
portal_user_KEYint
preferred_localenvarchar (50)NOT NULLPreferred locale for the contact used for language and formatting of dates, times, numbers when the locale is not available or if code running in another place needs to use it
time_zone_KEYsmallint (5)NOT NULLThe preferred timezone for the contact. Use this when displaying time to the user and the time zone is not known.
digita_entityiduniqueidentifierThe entity id is a unique identifier which is used to identify the same entity across products. Each product may have their own primary or identifying key for an entity. This identifier allows data for the same entity to flow between applications.
digita_metadatanvarchar (-1)The metadata is a block of xml (serialized object) which describes the scope of the entities data this product is interested in. This reduces the number of phantom changes being fired when changes are outside of the scope.
Primary key
NameColumnsDescription
PK_Contact$contact_KEYcontact_KEYCLUSTERED
Unique constraints
NameColumnsDescription
UK_Contact$contact_guidcontact_guidEach Contact must have its own contact_guid value.
Indexes
NameColumnsDescription
IX_Contact$contact_type_KEYcontact_type_KEYIndex supports foreign key FK_Contact__Contact_Type__contact_type_KEY
IX_Contact$mailing__contact_address_type_KEYmailing__contact_address_type_KEYIndex supports foreign key FK_Contact__Contact_Address_Type__mailing__contact_address_type_KEY
IX_Contact$portal_user_KEYportal_user_KEYIndex supports foreign key FK_Contact__Portal_User__portal_user_KEY
IX_Contact$primary__contact_address_type_KEYprimary__contact_address_type_KEYIndex supports foreign key FK_Contact__Contact_Address_Type__primary__contact_address_type_KEY
IX_Contact$primary__contact_email_type_KEYprimary__contact_email_type_KEYIndex supports foreign key FK_Contact__Contact_Email_Type__primary__contact_email_type_KEY
IX_Contact$primary__contact_phone_type_KEYprimary__contact_phone_type_KEYIndex supports foreign key FK_Contact__Contact_Phone_Type__primary__contact_phone_type_KEY
Foreign keys
NameColumnsReferenced tableDescription
FK_Contact__Portal_User__portal_user_KEYportal_user_KEYPortal_User
FK_Contact__Time_Zone__time_zone_KEYtime_zone_KEYTime_Zone
Incoming foreign keys
NameColumnsReferencing tableDescription
FK_Additional_Contact__Contact__child__contact_KEYchild__contact_KEYAdditional_Contact
FK_Additional_Contact__Contact__parent__contact_KEYparent__contact_KEYAdditional_Contact
FK_Contact_Address__Contact__contact_KEYcontact_KEYContact_Address
FK_Contact_Contact_Category__Contact__contact_KEYcontact_KEYContact_Contact_Category
FK_Contact_Email__Contact__contact_KEYcontact_KEYContact_Email
FK_Contact_Phone__Contact__contact_KEYcontact_KEYContact_Phone
FK_File_Transfer__Contact__contact__contact_KEYcontact__contact_KEYFile_Transfer
FK_File_Transfer__Contact__of__contact_KEYof__contact_KEYFile_Transfer
FK_File_Transfer__Contact__staff__contact_KEYstaff__contact_KEYFile_Transfer
FK_Legacy_Contact_Portal_Mapping__Contact__contact_KEYcontact_KEYLegacy_Contact_Portal_Mappingon delete cascade;
FK_Legacy_Contact_Portal_Mapping__Contact__primary__contact_KEYprimary__contact_KEYLegacy_Contact_Portal_Mapping
FK_Office__Contact__contact_KEYcontact_KEYOffice
FK_Staff__Contact__contact_KEYcontact_KEYStaff
FK_Client__Contact__billing__contact_KEYbilling__contact_KEYClient
FK_Client__Contact__contact_KEYcontact_KEYClient
FK_Client__Contact__preferred__contact_KEYpreferred__contact_KEYClient
FK_Client__Contact__referred_by__contact_KEYreferred_by__contact_KEYClient
FK_Interaction_Contact__Contact__contact_KEYcontact_KEYInteraction_Contacton delete cascade;
FK_Schedule_Item__Contact__of__contact_KEYof__contact_KEYSchedule_Item
FK_Schedule_Item__Contact__with__contact_KEYwith__contact_KEYSchedule_Item

Schema diagram