Database tables by name | table number
🛈 Note
Table numbers could be different between databases - depends on whether there are custom 3rd party tables. You must reference the sequence table column
TableNumber to be certain.| Name | Description | Number |
|---|---|---|
| access_script | Scripts to implement row-based access rules (sentry light) | 406 |
| activeuser | Currently logged-on users. This table contains encrypted license information. Changing it may disable login for all users and require intervention by SuperOffice support. Recommended use: for determining who is logged on, at what location, etc. | 28 |
| address | Contact and Person addresses | 7 |
| AddressFormat | Address formats for GUI and labels. See more information: Addressformat on http://techdoc.superoffice.com | 57 |
| ai_chat_turn | Contains AI Chatbot history - contains whole chat, not just what is sent to the chatbot. History is ready ordered by timestamp | 462 |
| AmountClass | Amount Class list for SuperOffice Sales Intelligence (Saint) - used to group sales by amounts, into bins (low —> high) called amount classes. More information regarding SuperOffice Sales Intelligence on http://techdoc.superoffice.com | 225 |
| AmountClassGroupLink | User group link table for AmountClass, for MDO item hiding | 226 |
| AmountClassHeadingLink | Heading link table for AmountClass, for MDO headers | 227 |
| 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. | 9 |
| area | Definition of an Area (database subset for satellite and travel) | 38 |
| areauserassignment | Link table indicating which users actually reside in this area. | 40 |
| areauserinclusion | Link table incidated whose data should be included in this area. If Include all data in Area (no filtering) is ticket then there will be no rows for this area in this table. | 41 |
| associate | Employees, resources and other users - except for External persons | 2 |
| AssociateGroupLink | User group link table for Associate, for MDO item hiding | 3 |
| AssociateHeadingLink | Heading link table for associate for display only. Supportive table, used for grouping and filtering on lists. | 4 |
| AssociateHistory | Historical information about associates that have been deleted. Most references are NOT declared as foreign keys; this is a historical table that should not be updated when further changes occur in the database | 526 |
| attachment | This table contains metadata for attachments. The actual attachments are stored directly on disk, with filenames based on the the primary key for this table. | 296 |
| attachment_location | A location for storing attachments | 476 |
| AudienceConfig | Configuration data for Audience core and webparts | 236 |
| AudienceLayout | One layout (of webparts and other stuff) for an audience instance | 234 |
| AudienceLayoutLink | Link between an audience layout and some target grouping table - might be Role or Category | 235 |
| AudienceVisibility | How projects (or whatever) should be made visible in audience | 232 |
| autosave | Autosaved text clobs from ejscript and emarketeer messages | 402 |
| BaseTZLocation | Time zone location for the database (how tz-related datetimes should be stored in the database) | 248 |
| BatchTask | Batch task request details, corresponding to the message body of a batch request message | 243 |
| BatchTaskDefinition | Batch task definitiopns, populated from the SuperOffice.CRM.BatchProcessing.BatchTask attribute | 244 |
| BinaryObject | Binary objects, i.e., blobs. Used for images, documents, SuperOffice inbox mail and other large binary items | 205 |
| BinaryObjectLink | Link table, connects a BinaryObject with one or more owners | 206 |
| board_view_settings | Settings for selection board view | 496 |
| Business | Business list table | 61 |
| BusinessGroupLink | User group link table for Business, for MDO item hiding | 62 |
| BusinessHeadingLink | Heading link table for Business, for MDO headers | 63 |
| CacheInvalidation | Names and generation numbers for distributed invalidation of caches | 527 |
| CacheTables | Specifies which tables should be cached to local files (or otherwise), generally these are the lists and other low-frequency-of-change tables. Contains the ID of any tables cached in SOCache. The files are binary and called <tablename>.bin. <Shift>+<F5> throws all cache files. | 148 |
| Category | Category list table | 64 |
| category_membership | This table connects users to categories (many-to-many). | 270 |
| CategoryFamily | Grouping table so that multiple company categories can be grouped under one term; to simplify searching for things like ‘all customers’ | 473 |
| CategoryGroupLink | User group link table for Category, for MDO item hiding | 65 |
| CategoryHeadingLink | Heading link table for Category, for MDO headers | 66 |
| cc_template | This table contains templates for the customer center | 478 |
| chat_message | This table contains messages in a chat session. | 333 |
| chat_session | This table contains chat sessions. | 332 |
| chat_topic | This table contains chat topics. | 330 |
| chat_topic_user | This table connected the chat topics with the users (i.e. the membership). | 331 |
| company | Information on license and owner of this SuperOffice database. This table should only have 1 row. This table contains encrypted license information. Changing it will disable login for all users and require you to restore the database from backup. | 1 |
| company_domain | This table contains web-domains associated with a certain cust_company entry. | 303 |
| Comptr | Comptr list table. List of all possible competitors (sale). | 109 |
| ComptrGroupLink | User group link table for Comptr, for MDO item hiding | 110 |
| ComptrHeadingLink | Heading link table for Comptr, for MDO headers | 111 |
| config | This table contains certain system-wide configuration values. | 255 |
| ConfigurableScreenAppliesTo | Mapping between recipes in scil and chosen type of data (appliesToKey) to differ layouts on | 465 |
| ConfigurableScreenDelta | Parts of recipes in SCIL to insert or remove in given recipes | 464 |
| ConnectionConfigField | Configuration data for Erp and Quote Connections | 421 |
| ConsentPerson | Link table that defines who has which consents | 472 |
| ConsentPurpose | GDPR purpose alternatives | 469 |
| ConsentSource | Consent source for GDPR | 471 |
| contact | Companies and Organizations. | 5 |
| contactinterest | Link-table between contact and interests in ContInt | 14 |
| ContInt | ContInt list table. List-text of all valid contact interest types. | 70 |
| ContIntGroupLink | User group link table for ContInt, for MDO item hiding | 71 |
| ContIntHeadingLink | Heading link table for ContInt, for MDO headers | 72 |
| CounterValue | Visible for rights | 197 |
| country | Country information | 19 |
| CountryGroupLink | User group link table for Country, for MDO item hiding | 20 |
| CountryHeadingLink | Heading link table for Country, for MDO headers | 21 |
| Credentials | Alternative credentials | 250 |
| Credited | Credited list table. List of who is to be credited for the sale. | 97 |
| CreditedGroupLink | User group link table for Credited, for MDO item hiding | 98 |
| CreditedHeadingLink | Heading link table for Credited, for MDO headers | 99 |
| Currency | Currency list table | 112 |
| CurrencyGroupLink | User group link table for Currency, for MDO item hiding | 113 |
| CurrencyHeadingLink | Heading link table for Currency, for MDO headers | 114 |
| cust_category | This table contains entries for categories exposed through a customer language. | 321 |
| cust_config | This table contains JSON structures used for customizing the customer center | 477 |
| cust_lang | This table contains entries for customer languages. | 320 |
| dashboard | Describes a dashboard | 479 |
| dashboard_theme | A set of style rules for the Dashboard | 480 |
| dashboard_tile | Represents one tile in the dashboard | 482 |
| dashboard_tile_definition | Describes the contents of a tile | 481 |
| dashboard_tile_field | Describes the contents of a tile field | 483 |
| DatabaseModel | New DatabaseModel used by Continuous Database | 456 |
| DataRight | Data right definition | 195 |
| dbi_agent | DBI agent settings | 381 |
| dbi_agent_field | DBI agent fields | 382 |
| dbi_agent_schedule | DBI agent schedule settings | 383 |
| DeliveryTerms | The list of Delivery terms, in the internal product register | 433 |
| DeliveryTermsGroupLink | User group link table for DeliveryTerms, for MDO item hiding | 434 |
| DeliveryTermsHeadingLink | Heading link table for DeliveryTerms, for MDO item headings | 435 |
| DeliveryType | The list of Delivery types, in the internal product register | 436 |
| DeliveryTypeGroupLink | User group link table for DeliveryType, for MDO item hiding | 437 |
| DeliveryTypeHeadingLink | Heading link table for DeliveryType, for MDO item headings | 438 |
| DiaryView | Configuration of a multi-user diary view | 214 |
| DiaryViewRow | Configuration of a multi-user diary view | 215 |
| dictionary | User added dictionary words | 358 |
| dictionary_base | Language catalog for the ejournal dictionaries (automatic proof reading of message text etc) | 359 |
| doc_document | This table contains documents. | 280 |
| doc_folder | A document folder. | 281 |
| DocTmpl | DocTmpl list table. Describes templates available for writing new documents. | 130 |
| DocTmplGroupLink | User group link table for DocTmpl, for MDO item hiding | 131 |
| DocTmplHeadingLink | Heading link table for DocTmpl, for MDO headers | 132 |
| document | Documents, this table is an extension of the Appointment table. There is always a corresponding appointment record; the relation between appointment and document is navigable in both directions. A document-type appointment record always has a corresponding document record and a record in VisibleFor specifying who may see this. | 10 |
| eab_entry | This table contains eab (email address book) entries, i.e. an alias ('Ola Hansen') and an address ('ola@hansen.as'). | 315 |
| eab_folder | This table contains eab (email address book) folders, used for containing email addresses. | 314 |
| ej_category | This table contains categories, in which tickets are categorized. The categories are organized in a hierarchial manner. | 257 |
| ej_message | This table contains the messages listed under tickets. | 258 |
| ej_role | Define access rights, memberships and other properties for role user members | 323 |
| EjCategoryGroupLink | User group link table for EjCategory, for mass handling ej_category members | 450 |
| ejpackage | This table stores packages on the system. | 384 |
| ejpackage_item | This table stores info on installed packages in the system | 385 |
| ejscript | ejscript | 377 |
| ejscript_debug | This table contains information when debugging an ejscript | 387 |
| ejsel_ejsel | This table defines sources for complex selections in a many/many relationship | 392 |
| ejsel_meta_result | This table stores result meta data | 397 |
| ejsel_result_set | This table stores result set reference data, result sets for selections | 398 |
| ejsel_source_idlist | This table stores id list source for selections | 393 |
| ejsel_source_script | This table stores a selection script source | 394 |
| ejsel_source_xml | This table stores a selection source as xml | 395 |
| ejselection | This table stores selections, dynamic groups. | 391 |
| ejuser | This table contains entries for the users of the system. | 299 |
| element_profile | The new (4.0) profile table. Contains profile for a single Html-element. Connected through element_profile_link | 328 |
| Email addresses for contacts, projects and persons | 55 | |
| email_account | Email account information | 487 |
| email_attachment | Attachment info related to an email_item | 491 |
| email_flow | A set of properties related to the email workflow. | 514 |
| email_flow_content_link | Links content to an email workflow | 521 |
| email_folder | Corresponds to an email folder on a mail server | 488 |
| email_item | Email data | 490 |
| EntityCounts | Number of different entities an associate has created for usage statistics | 534 |
| ErpConfiguration | Global settings for the Erp Integration Server | 449 |
| ErpConnection | One connection to an ERP connector, specifying Client and other required information | 418 |
| ErpConnectionAccess | Access control for Erp Connections | 420 |
| ErpConnectionActorType | Data about the configuration of one Erp Actor on one ErpConnection | 419 |
| ErpConnector | One ERP Connector, known by its URL | 417 |
| ErpExternalKey | The external (ERP-facing) key related to a synchronized record / connection | 423 |
| ErpField | Store the metadata describing the fields that belong to an actor/connection combination, as described by the Erp Connector | 425 |
| ErpInternalKey | The internal (superoffice-facing) key related to a synchronized record | 422 |
| ErpListItemMapping | Defines a mapping of ERP to CRM fields, per connection and actor type | 424 |
| ErpSyncLog | Record all field changes done by the Erp Sync | 426 |
| ext_datasource | This table contains external datasources, used for databaseintegration of customers and companies. | 317 |
| ext_field | This table contains entries mapping an external field to an internal field. Used for database integration. | 319 |
| ext_table | This table contains entries used for mapping an external table to an internal table (customer or cust_company) for database integration. | 318 |
| ExtApp | ExtApp list table. Applications startable from SuperOffice | 133 |
| ExtAppGroupLink | User group link table for ExtApp, for MDO item hiding | 134 |
| ExtAppHeadingLink | Heading link table for ExtApp, for MDO headers | 135 |
| external_document | This table stores documents which can be viewed externaly, through the customer module | 401 |
| ExternalEvent | The definition of projects as events in Audience (or other Collaborative apps) | 233 |
| extra_fields | This table contains entries for the extra fields in the system. | 304 |
| extra_menus | This table contains entries for the extra menus in the system. | 307 |
| extra_tables | This table contains entries for the extra tables in the system. | 305 |
| extra_tables_entry | Hits/entries in result set of executed search in ejournal extra tables | 309 |
| extra_tables_result | Result set of executed search in ejournal extra tables | 308 |
| Favourite | Favourite records (star-marking) | 455 |
| FieldLabel | Field label override table, makes it possible to override internal string resources. Define your own text for the panels in SuperOffice, e.g. rename Project to Cars in SOAdmin - System Options - Labels This table contains controlling data for the string substitution mechanism. There is one row in this table for each label or string that can be substituted; the active field indicates whether the string is actually being substituted or not. Initially, all rows have this field set to 0. The table is loaded with initial data during database setup. Only SuperOffice Development has the necessary expertise to safely add rows to this table. If a row has active = 1, the table LocaleText should contain one or more rows pointing back to this table, with the actual text to be used. | 168 |
| foreignapp | Top level of Foreign Key system | 181 |
| foreigndevice | Middle level of Foreign Key system | 182 |
| foreignkey | Foreign Key - enables storage of arbitrary extra key information for every table/row in SuperOffice. You may use this table to store your extra information instead of using the dictionary SDK to create your own tables. | 183 |
| form | A form which can be published on a webpage and submitted by visitors | 485 |
| form_field_value | Form field values saved in a searchable format | 525 |
| form_keys | Keys that makes sure a form is not posted twice | 366 |
| form_submission | A form submission | 486 |
| 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). | 46 |
| freetextstopwords | Here are the words that can be excluded from Free Text Search by using the FreeTextAdmin. The words that appear here will not be found in FreeTextWords and typically include “are”, “this”, “that”, and so on - words that occur frequently, but are not useful for searching. The more (good) stop words you have, the smaller the index will be. | 44 |
| freetextwords | This table contains the word list (automatically updated by the indexer) for the free-text search. Words are in UPPERCASE and truncated to 9 significant characters. Indexed words, dynamically updated by the freetext index | 45 |
| FunctionRight | Functional right definition | 193 |
| FunctionRightRoleLink | Functional right definition | 194 |
| Heading | Heading items for all MDO lists, lists that are grouped and filtered. | 58 |
| help | This table contains the help pages. | 302 |
| hierarchy | This table contains folders used to group the extra tables in the system. | 306 |
| History | History lists for lists and searchable controls. Maintains history for Navigator or other search (find dialogs). A single table may have more than one record here, as indicated by the extra_id field. The HistorySize (preference may be set in maintenance client) defines how many records you can have in a history list. | 53 |
| hotlist | The table is used by the hotlist to store the relationship between tickets and users | 363 |
| ImportDefault | Defaults for import fields/objects | 189 |
| ImportField | Import object types - see localetext for names | 187 |
| ImportObject | Import object types - see localetext for names. | 186 |
| ImportRelation | Relations between import objects | 188 |
| inbox | Info and status for safe email import | 352 |
| Intent | Intent list for SAINT. More information regarding SuperOffice Sales Intelligence on http://techdoc.superoffice.com | 216 |
| IntentGroupLink | User group link table for Intent, for MDO item hiding | 217 |
| IntentHeadingLink | Heading link table for Intent, for MDO headers | 218 |
| invitation | Invitations to events | 492 |
| invoice | This table contains invoice entries, normally created when an invoice is sent to a customer, and we want to update the balance. | 265 |
| invoice_entry | This table contain all invoices, connected to a message | 360 |
| 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. | 266 |
| invoice_type | A invoiceable item category (a product or service) that provides default invoice line values | 361 |
| item_config | This table is a generic table for storing item configuration. It is only used by the class ItemConfig. | 368 |
| kb_attachment | This table connects FAQ entries to attachments. | 284 |
| kb_category | Knowledge base folder hierarchy | 283 |
| kb_category_log | Who and when, if somebody edits a knowledge base folder | 291 |
| kb_entry | This table contains FAQ entries. | 282 |
| kb_entry_comment | Comments to entries in the knowledge base, typically made by customers | 289 |
| kb_entry_keyword | This table contains all keywords for the faq entries | 288 |
| kb_entry_log | Who and when, if somebody edits a knowledge base entry | 290 |
| kb_entry_words | This table contains all the words and how many times the are refered to in the FAQ entires | 354 |
| kb_group | This table contains FAQ groups. A group is a cluster of entries (potentially located anywhere in the FAQ hierarchy). A group is located in a certain category. | 286 |
| kb_group_entry | This table contains group entries for FAQ groups. | 287 |
| kb_http_link | This table contains URL's associated with a single FAQ entry. | 285 |
| kb_solution_finder | Knowledge base problem solving wizard, categories and subcategories for drilling down | 294 |
| kb_solution_finder_entry | Knowledge base problem solving wizard, items in a category linking to a knowledge base entry | 295 |
| kb_workflow | Knowledge base workflow steps | 292 |
| kb_workflow_access | Control of who can do what in a knowledge base workflow step | 293 |
| LanguageInfo | Information about languages, from ISO standards and related information | 210 |
| LanguageInfoCountry | Many-many link between countries and languages, to give intelligent choices for language | 211 |
| leadstatus | List items of lead status that is selectable for contacts and persons that have specific category | 536 |
| legal_html_tags | This table is used as a list of all legal HTML tags. HTML tags not in this list will be ignored when viewing html versions of messages | 353 |
| LegalBase | Legal base for GDPR (Article 6) | 470 |
| LicenseAssocLink | Link between ModuleLicense and Associate, for per-assoc licenses; this is how licenses are assigned/consumed | 238 |
| LicenseSatlLink | Link between License and Satellite, for per-database licenses | 239 |
| LocaleText | Multi-language text items. Used for user-defined field labels. Must be assigned correct name to match the language they start SuperOffice in. This table should be viewed in conjunction with FieldLabel. If a row in FieldLable has active = 1 this table will need to contain at least one row with the same resourceId as the FieldLabel row. The language id can be either 0 or one of the Windows language ID’s; SuperOffice will pick the correct language on startup according to the user settings. If a label cannot be found with the given language and also not with language 0, it will not be substituted. | 169 |
| locking | Generic locking and error messages | 380 |
| log_debug | A log used for debugging, especially useful for bLogic/ejscript | 365 |
| log_events | System log | 364 |
| login | This table contains entries for the user sessions. | 297 |
| login_customer | This table contains entries for customer sessions. At first only used for Soap logins, but will later also be used for web logins | 298 |
| mail_alias | This table contains the alias'es for each mailbox, one-to-many-relation. It is in so we can substract the alias'es when when listing the recipients of a message. | 273 |
| mail_block | This table controls the spam-protection system, ensuring that a single email recipient does not recieve too many emails during a certain period of time. | 316 |
| mail_in_filter | This table contains entries for the mailboxes the eJournal system is fetching mail from (POP3 or IMAP). | 271 |
| mail_in_uidl | This table is used to avoid spamming the system by importing the same message several times (normally a result of a crash somewhere). When a mailbox is openede, then unique id for each message is stored in this table, and then removed only when the message has been correctly imported and deleted from mailbox. | 272 |
| MailingDomains | List of allowed domains used in a Mailing | 494 |
| MergeMoveLog | Log of merge and move operations (person, contact, project) | 37 |
| Message | Definition of a message, corresponding to the header of a protocol | 242 |
| message_customers | This table contains all cutomers who are involved in a message | 260 |
| message_header | This table contains small pieces of information which is listed over the body for each message. | 259 |
| message_id | This table links an email message id to an eJournal item | 386 |
| MessageHandler | Presence and heartbeat of a message handler, should be updated once a minute. Older records are stale | 241 |
| ModuleLicense | Module licenses, belonging to one single owner | 237 |
| ModuleOwner | Unique owner of a set of licensed modules | 212 |
| MrMrs | MrMrs list table. List of salutations. | 94 |
| MrMrsGroupLink | User group link table for MrMrs, for MDO item hiding | 95 |
| MrMrsHeadingLink | Heading link table for MrMrs, for MDO headers | 96 |
| ms_filter | This table contains email filters. These are the filters allowing you to do advanced parsing of incomming emails. | 310 |
| ms_filter_mail | This table connects mail filters (ms_filter) to mailboxes (mail_in_filter). | 311 |
| ms_substitute | Regexp for extracting info from emails when they enter they system | 313 |
| ms_trashbin | This table contains entries for emails which have been trashed by a filter, waiting for confirmation of deletion or import. | 312 |
| notice_frame | PID controller for automatic adjustment of pop up message check rate | 404 |
| notify | This table contains the pop-up messages displayed for users for various events, such as 'new ticket', etc. | 301 |
| obsolete_1 | Obsolete table for functionality that was never implemented | 451 |
| obsolete_2 | Obsolete table for functionality that was never implemented | 452 |
| obsolete_3 | Obsolete table for functionality that was never implemented | 453 |
| obsolete_4 | Obsolete table for functionality that was never implemented | 454 |
| OLEField | Control data table for the OLE DB Provider | 165 |
| OLEFieldText | Control data table for the OLE DB Provider | 166 |
| OLESubject | Control data table for the OLE DB Provider | 161 |
| OLESubjectText | Control data table for the OLE DB Provider | 162 |
| OLEView | Control data table for the OLE DB Provider | 163 |
| OLEViewText | Control data table for the OLE DB Provider | 164 |
| OnlineApp | Echo and track information about Online Apps and their usage | 498 |
| outbox | Outgoing emails with sending status and other info | 351 |
| outgoing_message | Delivery of outgoing messages to messageplugins, updated with status asynchroneously | 407 |
| 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. | 167 |
| password_rules | This table may contain one entry specifying rules for passwords. | 322 |
| PaymentTerms | The list of payment terms, in the internal product register | 427 |
| PaymentTermsGroupLink | User group link table for PaymentTerms, for MDO item hiding | 428 |
| PaymentTermsHeadingLink | Heading link table for PaymentTerms, for MDO item headings | 429 |
| PaymentType | The list of payment types, in the internal product register | 430 |
| PaymentTypeGroupLink | User group link table for PaymentType, for MDO item hiding | 431 |
| PaymentTypeHeadingLink | Heading link table for PaymentType, for MDO item headings | 432 |
| PersInt | PersInt list table. List of Person interests. | 73 |
| PersIntGroupLink | User group link table for PersInt, for MDO item hiding | 74 |
| PersIntHeadingLink | Heading link table for PersInt, for MDO headers | 75 |
| person | Persons | 6 |
| personinterest | Note: If you add or remove rows in this table, you will need to update the interestCount field in the person table accordingly. This field should always reflect the number of interest records a person has, to enable the correct setting of the interest indicator on the tab in the person dialog. Replication note: The combination of person_id and pinterest_idx is unique. If a duplicate is made on a replicated database, the system will replace the record in the target database with the one derived from the source database during replication. Therefore, do not assume that a record in this table will retain its ID indefinitely, even if the person keeps the interest. | 15 |
| PersPos | PersPos list table. Contact person position list | 76 |
| PersPosGroupLink | User group link table for PersPos, for MDO item hiding | 77 |
| PersPosHeadingLink | Heading link table for PersPos, for MDO headers | 78 |
| phone | Contact and Person phonenumbers (+fax) | 8 |
| PhoneFormat | Formatting information for telephone numbers | 251 |
| PMembType | PMembType list table. List text of titles (member types) for project members. | 91 |
| PMembTypeGroupLink | User group link table for PMembType, for MDO item hiding | 92 |
| PMembTypeHeadingLink | Heading link table for PMembType, for MDO headers | 93 |
| PrefDesc | Preference description, drives the Preference GUI. Maintenance client - controls all preferences in SuperOffice. You find an overview off all standard preference on http://techdoc.superoffice.com. May be used by third-party developers to add system preferences to be updated from SuperOffice Maintenance client, instead of ini-files. | 184 |
| PrefDescLine | Preference description - multiple choice line - drives the Preference GUI. May be used by third-party developers to add system preferences to be updated from SuperOffice Maintenance client, instead of ini-files. | 185 |
| preference | Not quite obsolete preference table; historical info mostly. From 6.1 this table now holds an upgrade stamp. | 22 |
| PriceList | List of prices, cached from an ERP system | 128 |
| PriceUnit | The list of price units, in the internal product register (meter, ton, bushel, microsecond, gradus, τρυβλίον, 五合枡, دونم or whatever) | 439 |
| PriceUnitGroupLink | User group link table for PriceUnit, for MDO item hiding | 440 |
| PriceUnitHeadingLink | Heading link table for PriceUnit, for MDO item headings | 441 |
| Priority | Priority list table. Used with appointments: low, high. | 79 |
| PriorityGroupLink | User group link table for Priority, for MDO item hiding | 80 |
| PriorityHeadingLink | Heading link table for Priority, for MDO headers | 81 |
| Prob | Prob list table. Probability, used in sales . | 82 |
| ProbGroupLink | User group link table for Prob, for MDO item hiding | 83 |
| ProbHeadingLink | Heading link table for Prob, for MDO headers | 84 |
| Product | One Product, member of one price list | 129 |
| ProductCategory | List for the ProductCategory field of the Product table (Quote Management) | 408 |
| ProductCategoryGroupLink | User group link table for ProductCategory, for MDO item hiding | 409 |
| ProductCategoryHeadingLink | Heading link table for ProductCategory, for MDO item headings | 410 |
| ProductFamily | List for the ProductFamily field of the Product table (Quote Management) | 411 |
| ProductFamilyGroupLink | User group link table for ProductFamily, for MDO item hiding | 412 |
| ProductFamilyHeadingLink | Heading link table for ProductFamily, for MDO item headings | 413 |
| ProductType | List for the ProductType field of the Product table (Quote Management) | 414 |
| ProductTypeGroupLink | User group link table for ProductType, for MDO item hiding | 415 |
| ProductTypeHeadingLink | Heading link table for ProductType, for MDO item headings | 416 |
| ProductVersion | Version information for code modules. Owner + code module must be unique | 240 |
| profile | Deprecated. This table contains entries for the user profiles. | 329 |
| project | Projects | 11 |
| projectmember | Project members. Link-table between person and project | 12 |
| ProjectTypeStatusLink | Many-many link table between project type and status, similar to sale type-stage link; and an anchor point for guide items | 213 |
| ProjStatus | ProjStatus list table. Project status | 88 |
| ProjStatusGroupLink | User group link table for ProjStatus, for MDO item hiding | 89 |
| ProjStatusHeadingLink | Heading link table for ProjStatus, for MDO headers | 90 |
| ProjType | ProjType list table. List of valid Project types. | 85 |
| ProjTypeGroupLink | User group link table for ProjType, for MDO item hiding | 86 |
| ProjTypeHeadingLink | Heading link table for ProjType, for MDO headers | 87 |
| Publish | Publishing system for external users | 200 |
| PushNotificationService | Used for storing handles to user devices that should receive push notifications | 499 |
| quick_filter_info | Connect quick filter info from a specific provider to a dashboard | 484 |
| quick_reply | Personal quick reply text fragments | 463 |
| Quote | Quote root level, at most one per Sale, always connected to one Sale | 34 |
| QuoteAlternative | Quote Version is made up of one or more Alternatives. One of 1..n possible alternatives in a Quote Version. The reason we have alternatives is that a quote can say to a customer, “we can solve you problem in two (or more) different ways, with different technology and sideeffects (and price)”. An Alternative may have discounts on the total amount. The Alternative tracks whether the user on the order level entered the Discount , Earning amount or the TotalPrice fields so that the discount and earning and total can be re-calculated correctly when Quote Lines are added or changed. | 47 |
| QuoteApprReason | Predefined reasons for quote approval | 528 |
| QuoteApprReasonGroupLink | User group link table for QuoteApprReason, for MDO item hiding | 529 |
| QuoteApprReasonHeadingLink | Heading link table for QuoteApprReason, for MDO headers | 530 |
| QuoteConnection | Primary key in the CRM database. Definition of a connection to an external system, for the Quote system. | 26 |
| QuoteConnectionAccess | Access control for Quote Connections | 27 |
| QuoteDenyReason | Predefined reasons for quote denial | 531 |
| QuoteDenyReasonGroupLink | User group link table for QuoteDenyReason, for MDO item hiding | 532 |
| QuoteDenyReasonHeadingLink | Heading link table for QuoteDenyReason, for MDO headers | 533 |
| QuoteLine | One line in a QuoteAlternative. QuoteLines are mainly information copied from the Products provider. Products information is sometimes edited by the user before being included in the quote, so most information is duplicated from Product rather than referenced directly. | 127 |
| QuoteLineConfiguration | Configuration of quote lines - which fields are in use, rights, labels etc | 445 |
| QuoteVersion | There may be multiple Versions of a Quote, with one of them active | 39 |
| QuoteVersionAttachment | Actual attachments to a quote | 447 |
| Reason | Reason list table. Why we lost the sale (list) | 103 |
| ReasonGroupLink | User group link table for Reason, for MDO item hiding | 104 |
| ReasonHeadingLink | Heading link table for Reason, for MDO headers | 105 |
| ReasonSold | Why was the sale marked as sold (why did we succeed) | 115 |
| ReasonSoldGroupLink | User group link table for ReasonSold, for MDO item hiding | 116 |
| ReasonSoldHeadingLink | Heading link table for ReasonSold, for MDO headers | 117 |
| ReasonStalled | Why was the sale marked as stalled | 154 |
| ReasonStalledGroupLink | Link table for ReasonStalled, for MDO item hiding | 155 |
| ReasonStalledHeadingLink | Heading link table for ReasonStalled, for MDO headers | 156 |
| RecurrenceRule | The recurrency pattern for a recurring event. Each recurring event has an appointment.recurrenceRuleId pointing to its pattern. | 207 |
| redletterday | Red letter days for calendar (holidays, birthday of king etc) | 17 |
| RefCountRange | Number allocation system, for keeping track of ranges of numbers loaned out to travel and satellite databases | 172 |
| RefCounts | Number counter for all tables that generate numbers, e.g. templates, contacts… This table is used for the number allocation system and should not be confused with sequence, used for allocating internal ID’s. This table is replicated during generation of satellites and during local update for travellers, using special logic. By default it contains rows for the SuperOffice standard counters, including one row for each DocTemplate record. It is permissible to add new rows to this table, and such records are maintainable through the Maintenance client. Changing the contents of the standard records is not recommended. | 171 |
| registry | System settings | 253 |
| RejectReason | Rejection reason (suggested) for bookings | 222 |
| RejectReasonGroupLink | User group link table for Comptr, for MDO item hiding | 223 |
| RejectReasonHeadingLink | Heading link table for RejectReason, for MDO headers | 224 |
| relationdefinition | Definition of a relation. This table defines the relations that can exist in the database. Each relation has an active text and a passive text. The table RelationTarget specifies which pairs of tables this relation can connect. Use of the active and passive texts is dependent on which direction the relation is viewed in, e.g., active text = “Owns” and passive text = “Is owned by”. | 48 |
| relations | Instance of a relation, in principle between any two records, as long as they are defined in RelationDefinition. All instances of relations are held in this table; their definitions are in the RelDef table (RelDef + RelTarg define which relations you can have, this table contains the relations the user has actually entered). From 6.1 all links between appointments, sales and documents are also stored in this tabel. | 52 |
| relationtarget | Definition of targets for a relation. Links a relation definition (RelDef) to source and target tables. In general, a relation can be created between any pair of tables. This table is used for specifying which table pairs a particular relation can be used for. A relation definition should have at least one row in this table, and can have more. Note: The 5.0 Maintenance and GUI only support contact and person as valid values for the source_table and destination_table fields, in any combination. Other relations will not be shown, and relation definitions pointing to other tables will not be editable from the Maintenance GUI; however, nothing will crash. | 51 |
| RelDefGroupLink | User group link table for RelDef, for MDO item hiding | 49 |
| RelDefHeadingLink | Heading link table for RelDef, for MDO headers | 50 |
| reply_template | Templates for automatic and manual replies to emails/sms organized hierachically | 277 |
| reply_template_attachment | This table is used to connect attachments to reply templates (many-to-many). | 278 |
| reply_template_body | Contains the body of the reply templates in different languages | 279 |
| reply_template_folder | This table contains entries for folders for reply templates. | 276 |
| ReporterListDef | Reporter definitions | 170 |
| ResourceOverride | Generic mechanism for overriding (or even defining new) text resources, in multiple languages | 448 |
| Role | User roles for role-based security, names and tooltips are in LocaleText. For more information regarding role based security, see http://techdoc.superoffice.com | 191 |
| role_category | Category membership associated with a role | 325 |
| role_element | Profiles associated with a role | 326 |
| role_member | Users linked to a role. Deprecated. | 324 |
| role_workflow | Knowledge base workflow access rights associated with a role | 327 |
| s_attachment | A connector between a message and attachments. One message can contain many attachments. | 349 |
| s_bounce_shipment | Email bounces from customers | 342 |
| s_dyn_criteria | Contains criterias for a dynamic list. | 350 |
| s_link | Links in messages to measure success rate of a campaign. | 336 |
| s_link_customer | A connection between a customer and a link. Registered customers are identified when clicking on a link | 337 |
| s_link_customer_statical | A connection between a customer and a link. Registered customers are identified when clicking on a link | 338 |
| s_list | A list, dynamic or static | 344 |
| s_list_customer | Elements in a customer list. | 346 |
| s_list_element | Elements in a static list. | 345 |
| s_list_shipment | A connector between shipment and list so that one shipment can have many lists, and one list can have many shipments | 348 |
| s_message | A message used in a shipment. Can be html and/or plain text | 335 |
| s_messageblock | Contains a block of a mailing message, that can be reused in a mailing | 493 |
| s_picture_entry | This table describes each picture in the database | 340 |
| s_picture_folder | This table contains all picture folders | 339 |
| s_sent_message | Emarketeer message control | 405 |
| s_shipment | Contains info about one shipment. The addresses are stored in s_shipment_addr | 334 |
| s_shipment_addr | Addresses that are ready to be sent in a shipment. | 347 |
| s_smtp_servers | Contains the smtp server for a shipment | 390 |
| s_washing | Register of all bounced mail to enabel washing | 341 |
| s_washing_list | Unused table that is ment to be used for active washing in spm v2 | 343 |
| SaintConfiguration | Configuration information for the Saint system | 458 |
| 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. | 13 |
| 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. | 157 |
| SaleStakeholder | Stakeholders in the sale, very similar to project members | 121 |
| SaleType | Type of sale - large solution, incremental, whatever fits the organization | 149 |
| SaleTypeCat | Category for sale type | 118 |
| SaleTypeCatGroupLink | User group link table for SaleTypeCat, for MDO item hiding | 119 |
| SaleTypeCatHeadingLink | Heading link table for SaleTypeCat, for MDO headers | 120 |
| SaleTypeGroupLink | User group link table for SaleType, for MDO item hiding | 150 |
| SaleTypeHeadingLink | Heading link table for SaleType, for MDO headers | 151 |
| SaleTypeQuoteAttachment | Default attachments to quotes linked to sales of this type | 446 |
| SaleTypeStageLink | Many-many link table between sale type and stage; and an anchor point for guide items | 160 |
| Salutation | Academic title for Person | 219 |
| SalutationGroupLink | User group link table for Salutation, for MDO item hiding | 220 |
| SalutationHeadingLink | Heading link table for Salutation, for MDO headers | 221 |
| satellite | Definition of Satellites | 42 |
| schedule | Generic scheduled tasked handling time scheduling, locking and error messages | 379 |
| scheduled_task | A scheduled entry executing a script at certain times | 376 |
| screen_chooser | Screen choosers | 375 |
| screen_definition | A configurable screen | 370 |
| screen_definition_action | An action to perform for a certain button in an screen | 371 |
| screen_definition_element | An element in a configurable screen | 372 |
| screen_definition_hidden | The name of a hidden variable to keep for this screen | 373 |
| screen_definition_language | Custom language variables used for screens | 374 |
| script_trace | Scripts which should be traced | 474 |
| script_trace_run | Traces of executed scripts | 475 |
| SearchCat | SearchCat list table | 106 |
| SearchCatGroupLink | User group link table for SearchCat, for MDO item hiding | 107 |
| SearchCatHeadingLink | Heading link table for SearchCat, for MDO headers | 108 |
| SearchCriteria | Criteria storage for Selection and other Find mechanisms | 201 |
| SearchCriteriaGroup | Criteria storage for Selection and other Find mechanisms | 202 |
| SearchCriterion | Criteria storage for Selection and other Find mechanisms | 203 |
| SearchCriterionValue | Criteria storage for Selection and other Find mechanisms | 204 |
| selection | Selections | 23 |
| 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. | 24 |
| sequence | next_id to be used for each table | 0 |
| service_auth | Authentication for a service (imap, smtp…) | 489 |
| session_object | Generic session object, accessible from ejscript etc, typically xml or name=value syntax, may be stored over several rows if big | 254 |
| ShipmentType | Shipment type list table. Classification of a mailing, allowing recipients to subscribe to lists | 500 |
| ShipmentTypeReservation | ShipmentTypes a person has reserved against. Note that the absense of a record here implies acceptance of a mailings of this type | 501 |
| sms | This table will hold outgoing sms messages when transmitted with WebServices | 388 |
| sms_hysteria | Avoid sending too many sms messages in a short time interval to one person | 367 |
| snapshot | Snapshots taken of the system database and attachments via soap | 369 |
| soap_access | Table that contains constraints on the access to the soap interface | 362 |
| SORCriteria | SuperOffice reporter data | 175 |
| SORFCT | SuperOffice reporter data | 178 |
| SORField | SuperOffice reporter data | 179 |
| SORLabelLayout | SuperOffice reporter data | 180 |
| SOROperators | SuperOffice reporter data | 176 |
| SORPublish | SuperOffice reporter data | 174 |
| SORPublishGroupLink | Link table used for filtering reports by user group | 25 |
| SORSection | SuperOffice reporter data | 177 |
| SORTemplate | SuperOffice reporter data | 173 |
| Source | Source list table. Source for sale (list) | 100 |
| SourceGroupLink | User group link table for Source, for MDO item hiding | 101 |
| SourceHeadingLink | Heading link table for Source, for MDO headers | 102 |
| StakeholderRole | Role a stakeholder has in a sale | 122 |
| StakeholderRoleGroupLink | User group link table for StakeholderRole, for MDO item hiding | 123 |
| StakeholderRoleHeadingLink | Heading link table for StakeholderRole, for MDO headers | 124 |
| static_list_ref | This table stores id references for selections id lists | 396 |
| StatusDef | Status definitions. Name and description are in LocaleText for internationalization | 198 |
| StatusValue | Values for statuses | 199 |
| SubscriptionUnit | The list of Subscription units, in the internal product register (year/quarter/month etc., or perhaps amounts if volume-based subscription) | 442 |
| SubscriptionUnitGroupLink | User group link table for SubscriptionUnit, for MDO item hiding | 443 |
| SubscriptionUnitHeadingLink | Heading link table for SubscriptionUnit, for MDO item headings | 444 |
| SuggestedAppointment | Defines a suggested appointment for use in a Sale Guide or Project Guide | 125 |
| SuggestedDocument | Unique owner of a set of licensed modules | 126 |
| SuperListColumnSize | Stores the relative size (in percent) or in characters of a column in a SuperList | 209 |
| system_script | A table containing the system script | 378 |
| SystemEvent | System events, such as freetext rebuild, SAINT rebuild and such. Makes broadcasts to keep its siblings and clients updated. | 153 |
| TabOrder | Order of tabs within a tab control, if configured by a user | 152 |
| Tags | MDO List of tags for Service entities | 459 |
| TagsGroupLink | User group link table for Tags, for MDO item hiding | 460 |
| TagsHeadingLink | Heading link table for Source, for MDO headers | 461 |
| target_assignment_info | Linking associate, company or user group target and other information with target values | 505 |
| target_assignment_value | A set of values linked to assignment info and a period in a target group. | 506 |
| target_change | A single field change. | 509 |
| target_dimension | Defining target dimension | 510 |
| target_group | Info about a set of (sales, project, selection…) targets | 503 |
| target_period | A set of periods linked with target amounts for users/usergroups and the target groups/years. | 504 |
| target_revision | One batch of changes made to targets | 508 |
| target_revision_history | Revision history info in case the original target group or assignment info was deleted | 507 |
| Task | Task list table, activity types, like Phone, Meeting | 67 |
| TaskGroupLink | User group link table for Task, for MDO item hiding | 68 |
| TaskHeadingLink | Heading link table for Task, for MDO headers | 69 |
| TaskMenu | List items to merge into menues | 466 |
| TaskMenuGroupLink | User group link table for TaskMenu, for MDO item hiding | 467 |
| TaskMenuHeadingLink | Heading link table for TaskMenu, for MDO headers | 468 |
| temp_db_lock | Represents a temporary lock on a resource identified by table_id and key | 522 |
| temporary_words | This table is used as a temporary table, containing the words we want to search for in the FAQs | 356 |
| TemporaryKey | Temporary keys for lightweight authentications such as changing ones subscriptions | 502 |
| text | Long text fields from all over the system | 18 |
| ticket | This table contains the tickets (requests) of the system. Its purpose should be evident. | 262 |
| ticket_alert | This table will contain ticket escalation levels. A ticket will be escalated along a 'chain' of these levels. | 274 |
| ticket_attachment | This table connects an attachment to a message. It references the entry in the attachment table, and the message. | 256 |
| ticket_customers | This table allows several customers to be connected to several tickets (many-to-many) | 264 |
| ticket_log | This table contains log entries for the tickets. | 267 |
| ticket_log_action | This table contains actions for the tickets. | 269 |
| ticket_log_change | This table contains log entries for the tickets. | 268 |
| ticket_priority | This table contains the ticket priorities. | 275 |
| ticket_status | This table user defined ticket status values. | 263 |
| ticket_status_history | This table contains the history of a tickets statuses. Each time a ticket changes status a copy of the previous status of the record will be saved | 261 |
| ticket_type | A ticket (request) type | 537 |
| ticket_type_priority | Link table defining what Priorities are relevant to a particular Ticket type | 538 |
| ticket_type_status | Link table defining what Statuses are relevant to a particular Ticket type | 539 |
| time_keeping | Time keeping for how much time a sale or project or other entity has spent in a given stage or other state | 497 |
| timestamps | Timestamp information | 300 |
| travelcurrent | Information about this database and its place in the hierarchy | 32 |
| travelgenerateddatabase | Information about all databases generated from this database | 33 |
| travelgeneratedtransaction | Record of all generated replication data files from this database (*.dwn files from mother database to child, *.up from child database to mother) | 30 |
| travelidmapping | Mapping of primary keys between Travel databases and the mother database All travel database transactions get a high id to be able to see that this entry came from a database outside the central database. When update files are read into the central database, they get a normal low id. This table remembers the high travel id to map it to the low central id as long as this travel user is travelling. | 43 |
| traveller | Associates traveling out from this database | 31 |
| traveltransactionlog | Log of all updates made to the database, that need to be replicated. | 29 |
| TrayApp | Tray application presence. SuperOffice CRM web extensions. | 252 |
| tree_explorer_entry | This table stores the entries in a tree-explorer | 399 |
| tree_explorer_link | This table stores the link of entries in a tree-explorer | 400 |
| TypicalSearch | Owner of a set of predefined selection criteria | 495 |
| TZDstRule | Time zone rule for daylight saving time | 247 |
| TZLocation | Time zone location | 245 |
| TZStdRule | Time zone rule for standard time | 246 |
| udappntlarge | User-defined fields | 229 |
| udappntsmall | User-defined fields | 228 |
| udcontactLarge | User-defined fields for contact (long strings) | 36 |
| udcontactSmall | User-defined fields for contact | 35 |
| uddoclarge | User-defined fields | 231 |
| uddocsmall | User-defined fields | 230 |
| UDefField | Definition table for user-defined fields; one row in this table corresponds to one generation of one field. The user defined fields that are in use, and earlier versions of user defined fields. ColumnId refers to the field type; see UDXXXSmall or UDXXXLarge for the referring ID. Preferences prefsection=‘System’, prefkey=‘CurrentUdefVersioncontact’ (or CurrentUdefVersionperson, project, sale), gives you the current version of user defined fields. prefkey=‘AdminUdefVersion<…>’ gives you the current version that’s being edited. If Current version = admin version, no editing has been done since the last Publish of user defined field was performed. | 146 |
| UDefFieldGL | User group link table for UDefField, for MDO item hiding | 147 |
| UDList | List table for user-defined lists, contains all user-defined lists. Note - MDO mode for userdefinede lists are either turned on or off, you may not have it on for one userdefined list and off for the others. | 136 |
| UDListDefinition | List table that contains the list of user-defined lists, as well as system-defined lists. The list items are stored in the UDList table. | 139 |
| UDListGroupLink | User group link table for UDList, for MDO item hiding. Note - MDO mode for userdefinede lists are either turned on or off, you may not have it on for one userdefined list and off for the others. | 137 |
| UDListHeadingLink | Heading link table for UDList, for MDO headers. Note - MDO mode for userdefinede lists are either turned on or off, you may not have it on for one userdefined list and off for the others. | 138 |
| udpersonLarge | User-defined fields | 141 |
| udpersonSmall | User-defined fields | 140 |
| udprojectLarge | User-defined fields. During conversion of user defined fields the data is stored in this table. | 143 |
| udprojectSmall | User-defined fields | 142 |
| udsalelarge | User-defined fields | 159 |
| udsalesmall | User-defined fields | 158 |
| udtempLarge | User-defined fields | 145 |
| udtempSmall | User-defined fields. During conversion of user defined fields the data is stored in this table. | 144 |
| URL | Unified Resource Locators, URL to contacts, persons or projects. | 54 |
| UsageStats | Usage statistics | 190 |
| user_attribute | This table is used for storing various attributes for users. | 403 |
| user_candidate | This table will hold user candidate secrets | 389 |
| UserGroup | Secondary user groups | 59 |
| UserGroupLink | Link table between associate and usergroup, specifies secondary group membership. From SIX an associate may belong to more than one usergroup. Http://techdoc.superoffice.com has more information about how roles are implemented. | 60 |
| UserPreference | Preference system. If deflevel is set to 5; the user may change the preferences | 56 |
| UserRoleLink | Link between user role and user | 192 |
| utm_parameters | Table for utm parameters collected from visits and formsubmissions | 535 |
| VisibleFor | Visible for rights, who may see this appointment/document, sale, salehist or selection | 196 |
| WebAppUsage | Usage statistics for web applications | 249 |
| Webhook | Webhook URL to call when events occur in the client or in NetServer. Also tracks call+error statistics. | 511 |
| Webhook_usage | Webhook usage statistics - tracks call+error statistics. Same primary key as the webhook. | 512 |
| WinPosSize | Stores the position and size of each window, so they can be shown in the same place again | 208 |
| word_relations | This table shows which word are used in which FAQ entry, and how many times they are used in each | 355 |
| workflow | SuperOffice specific info about a workflow | 513 |
| workflow_goal | A set of goals related to a workflow. Some goals will have search criterias associated with it to determine if the goal has been reached. | 516 |
| workflow_instance | A set of properties related to the workflow instance of one participant going through the flow | 515 |
| workflow_root_step_link | Link root steps to the workflow | 524 |
| workflow_step | A set of steps related to a workflow. | 517 |
| workflow_step_option | Some steps can have optional child ‘flows’, a new series of steps | 519 |
| workflow_step_option_link | Link steps to other steps through step options | 520 |
| workflow_trigger | A set of triggers related to a workflow. | 518 |
| workflow_wait_for_action | Some steps wait for actions, this is info about those actions | 523 |
| wsdl_description | Soap wsdl files | 357 |
| ziptocity | Zip codes and city names. Zip codes used during address entry. You will find more information about addressformat on http://techdoc.superoffice.com | 16 |