• Share
    • Twitter
    • LinkedIn
    • Facebook
    • Email
  • Feedback
  • Edit
Show / Hide Table of Contents

contact Table (5)

Some tooltip text!
• 8 minutes to read
 • 8 minutes to read

Companies and Organizations. This table features a special record containing information about the contact that owns the database.

Fields

Name Description Type Null
contact_id Primary key PK
name Contact name String(219)
kananame Contact kana name, used in Japanese versions only String(219) ●
department Department String(219) ●
number1 Alphanumeric user field String(49) ●
number2 Alphanumeric user field String(49) ●
associate_id Our contact FK associate ●
country_id Country FK country
business_idx Link to Business FK Business
category_idx Link to Category FK Category
xstop STOP flag Bool ●
nomailing No mailings flags Bool ●
registered Date registered UtcDateTime
registered_associate_id Registered by whom FK associate
updated Date last updated UtcDateTime
updated_associate_id Last updated by whom FK associate
text_id Paperclip note FK text ●
mother_id Reserved FK contact ●
userdef_id User defined table record 1 FK udcontactSmall ●
orgNr VAT number or similar String(49) ●
soundEx What the name sounds like, for duplicate detection String(9) ●
source How did we get this contact? For future integration needs UShort ●
userdef2_id User defined table record 2 FK udcontactLarge ●
activeInterests Number of records in cintr table; select count(*) from cintr ci where ci.contact_id = this.contact_id == activeInterests is always true UShort ●
updatedCount Number of times updated UShort
group_id Group id of original owning associate, semantics like appnt.grp_id FK UserGroup ●
tzLocationId Default timezone location for this contact FK TZLocation ●
ticketPriorityId Default ticket priority for new tickets FK ticket_priority ●
deleted If nonzero, then this contact is 'deleted' and should generally not be shown UShort ●
supportLanguageId Customers language (does not necessarily map to ISO languages) FK cust_lang ●
supportAssociateId Our contact, but for support context, not sales/primary contact FK associate ●
supportPersonId The person (at the customer) who support talks to (the counterpart of supportAssociateId) FK person ●
dbi_agent_id Integration agent (eJournal) FK dbi_agent ●
dbi_key The primary key for the integrated entry in the external datasource. String(255) ●
dbi_last_syncronized Last external syncronization. DateTime ●
dbi_last_modified When the entry was last modified. DateTime ●
activeErpLinks The number of Erp Sync connections this record is synced with; count of the ErpExternalKey+ErpInternalKey relations Int ●
DeletedDate Datetime (utc) when this record was soft-deleted; if this value is set then the record should not be shown UtcDateTime ●

contact table relationship diagram

Indexes

Fields Types Description
contact_id PK Clustered, Unique
name String(219) Index
kananame String(219) Index
department String(219) Index
number1 String(49) Index
number2 String(49) Index
business_idx FK Index
category_idx FK Index
mother_id FK Index
userdef_id FK Index
orgNr String(49) Index
soundEx String(9) Index
source UShort Index
userdef2_id FK Index
dbi_agent_id FK Index
dbi_key String(255) Index
dbi_last_syncronized DateTime Index
dbi_last_modified DateTime Index
name, department String(219), String(219) Index
DeletedDate UtcDateTime Index
supportPersonId FK Index

Relationships

Table Description
address Contact and Person addresses
appointment Tasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this.
associate Employees, resources and other users - except for External persons
Business Business list table
Category Category list table
chat_session This table contains chat sessions.
company_domain This table contains web-domains associated with a certain cust_company entry.
contact Companies and Organizations. This table features a special record containing information about the contact that owns the database.
contactinterest Link-table between contact and interests in ContInt
CounterValue Visible for rights
country Country information
cust_lang This table contains entries for customer languages.
dbi_agent DBI agent settings
Email Email addresses for contacts, projects and persons
email_item Email data
form_submission A form submission
freetextindex This 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).
invoice This table contains invoice entries, normally created when an invoice is sent to a customer, and we want to update the balance.
invoice_sum This table is used temporarily when listing invoice statistics. It is used because we need to sort balances from both customers and companies.
OwnerContactLink Table 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.
person Persons in a company or an organizations. All associates have a corresponding person record
phone Contact and Person phonenumbers (+fax)
projectmember Project members. Link-table between person and project
s_shipment_addr Addresses that are ready to be sent in a shipment.
sale Sales 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.
SaleHist Mirror 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.
SaleStakeholder Stakeholders in the sale, very similar to project members
satellite Definition of Satellites
selectionmember Selection 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.
StatusValue Values for statuses
target_assignment_info Linking associate, company or user group target and other information with target values
target_revision_history Revision history info in case the original target group or assignment info was deleted
text Long text fields from all over the system
ticket This table contains the tickets (requests) of the system. Its purpose should be evident.
ticket_priority This table contains the ticket priorities.
TZLocation Time zone location
udcontactLarge User-defined fields for contact (long strings)
udcontactSmall User-defined fields for contact
URL Unified Resource Locators, URL to contacts, persons or projects.
UserGroup Secondary user groups

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.
© SuperOffice. All rights reserved.
SuperOffice |  Community |  Release Notes |  Privacy |  Site feedback |  Search Docs |  About Docs |  Contribute |  Back to top