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