contact Table (5)

Companies and Organizations.

Fields

NameDescriptionTypeNull
contact_idPrimary keyPK
nameContact nameString(219)
kananameContact kana name, used in Japanese versions onlyString(219)
departmentDepartmentString(219)
number1Alphanumeric user fieldString(49)
number2Alphanumeric user fieldString(49)
associate_idOur contactFK associate
country_idCountryFK country
business_idxLink to BusinessFK Business
category_idxLink to CategoryFK Category
xstopSTOP flagBool
nomailingNo mailings flagsBool
registeredDate registeredUtcDateTime
registered_associate_idRegistered by whomFK associate
updatedDate last updatedUtcDateTime
updated_associate_idLast updated by whomFK associate
text_idPaperclip noteFK text
mother_idReservedFK contact
userdef_idUser defined table record 1FK udcontactSmall
orgNrVAT number or similarString(49)
soundExWhat the name sounds like, for duplicate detectionString(9)
sourceHow did we get this contact? For future integration needsUShort
userdef2_idUser defined table record 2FK udcontactLarge
activeInterestsNumber of records in cintr table; select count(*) from cintr ci where ci.contact_id = this.contact_id == activeInterests is always trueUShort
updatedCountNumber of times updatedUShort
group_idGroup id of original owning associate, semantics like appnt.grp_idFK UserGroup
tzLocationIdDefault timezone location for this contactFK TZLocation
ticketPriorityIdDefault ticket priority for new ticketsFK ticket_priority
deletedIf nonzero, then this contact is ‘deleted’ and should generally not be shownUShort
supportLanguageIdCustomers language (does not necessarily map to ISO languages)FK cust_lang
supportAssociateIdOur contact, but for support context, not sales/primary contactFK associate
supportPersonIdThe person (at the customer) who support talks to (the counterpart of supportAssociateId)FK person
dbi_agent_idIntegration agent (eJournal)FK dbi_agent
dbi_keyThe primary key for the integrated entry in the external datasource.String(255)
dbi_last_syncronizedLast external syncronization.DateTime
dbi_last_modifiedWhen the entry was last modified.DateTime
activeErpLinksThe number of Erp Sync connections this record is synced with; count of the ErpExternalKey+ErpInternalKey relationsInt
DeletedDateDatetime (utc) when this record was soft-deleted; if this value is set then the record should not be shownUtcDateTime

contact table relationship diagram

Indexes

FieldsTypesDescription
contact_idPKClustered, Unique
nameString(219)Index
kananameString(219)Index
departmentString(219)Index
number1String(49)Index
number2String(49)Index
business_idxFKIndex
category_idxFKIndex
mother_idFKIndex
userdef_idFKIndex
orgNrString(49)Index
soundExString(9)Index
sourceUShortIndex
userdef2_idFKIndex
dbi_agent_idFKIndex
dbi_keyString(255)Index
dbi_last_syncronizedDateTimeIndex
dbi_last_modifiedDateTimeIndex
name, departmentString(219), String(219)Index
DeletedDateUtcDateTimeIndex
supportPersonIdFKIndex

Relationships

TableDescription
addressContact and Person addresses
appointmentTasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this.
associateEmployees, resources and other users - except for External persons
BusinessBusiness list table
CategoryCategory list table
chat_sessionThis table contains chat sessions.
company_domainThis table contains web-domains associated with a certain cust_company entry.
contactCompanies and Organizations.
contactinterestLink-table between contact and interests in ContInt
CounterValueVisible for rights
countryCountry information
cust_langThis table contains entries for customer languages.
dbi_agentDBI agent settings
EmailEmail addresses for contacts, projects and persons
email_itemEmail data
form_submissionA form submission
freetextindexThis is the index table for the free text search function. Each word in FreeTextWords can have multiple occurrences in this table. Each record in this table points to one occurrence of the word, and points to both the table in which the word occurs (which might be contact or text), and also a pointer to the owner table (which is one of contact, person, project, appointment or sale).
invoiceThis table contains invoice entries, normally created when an invoice is sent to a customer, and we want to update the balance.
invoice_sumThis table is used temporarily when listing invoice statistics. It is used because we need to sort balances from both customers and companies.
notifyThis table contains the pop-up messages displayed for users for various events, such as 'new ticket', etc.
OwnerContactLinkTable specifying which contacts can own associates. All contacts that have rows in this table (i.e. rows with contact_id pointing to them) will be offered as associate owners in the maintenance client and as candidate Satellite owners. Such contacts have restrictions on editing and deletion to protect database consistency.
personPersons
phoneContact and Person phonenumbers (+fax)
projectmemberProject members. Link-table between person and project
s_shipment_addrAddresses that are ready to be sent in a shipment.
saleSales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels.
SaleHistMirror image of the Sale table, providing a full transaction history. Every time you edit a sale, the current record of the sale is also saved here.
SaleStakeholderStakeholders in the sale, very similar to project members
satelliteDefinition of Satellites
selectionmemberSelection detail table Each row in a selection is represented by one record in this table. Contact_id is always filled in, person_id is optional, but if used, must point to a person belonging to the contact in contact_id.
StatusValueValues for statuses
target_assignment_infoLinking associate, company or user group target and other information with target values
target_revision_historyRevision history info in case the original target group or assignment info was deleted
textLong text fields from all over the system
ticketThis table contains the tickets (requests) of the system. Its purpose should be evident.
ticket_priorityThis table contains the ticket priorities.
TZLocationTime zone location
udcontactLargeUser-defined fields for contact (long strings)
udcontactSmallUser-defined fields for contact
URLUnified Resource Locators, URL to contacts, persons or projects.
UserGroupSecondary user groups
utm_parametersTable for utm parameters collected from visits and formsubmissions
workflow_instanceA set of properties related to the workflow instance of one participant going through the flow

Replication Flags

  • Area Management controlled table. Contents replicated to satellites and traveller databases.
  • Replicate changes UP from satellites and travellers back to central.
  • Copy to satellite and travel prototypes.
  • Cache table during filtering.

Security Flags

  • Sentry controls access to items in this table using user’s Role and data rights matrix.