Tables are the fundamental building blocks of the ServiceNow platform, serving as the primary data storage mechanism similar to tables in traditional relational databases. Each table consists of rows (records) and columns (fields) that store specific types of information. In ServiceNow, tables are …Tables are the fundamental building blocks of the ServiceNow platform, serving as the primary data storage mechanism similar to tables in traditional relational databases. Each table consists of rows (records) and columns (fields) that store specific types of information. In ServiceNow, tables are used to organize and manage data for various applications, including incidents, problems, changes, and custom business processes.
Table Administration involves managing the structure, properties, and relationships of tables within the ServiceNow instance. System Administrators access table administration through the System Definition module, where they can create new tables, modify existing ones, and configure table properties.
Key aspects of Table Administration include:
1. **Table Creation**: Administrators can create custom tables to store application-specific data. Tables can extend existing tables, inheriting fields and functionality from parent tables.
2. **Field Management**: Adding, modifying, or removing columns (fields) from tables. Fields have various types including string, integer, reference, date/time, and choice lists.
3. **Table Properties**: Configuration options include setting the table label, plural label, access controls, and whether the table is extensible or audited.
4. **Table Relationships**: Tables can reference other tables through reference fields, creating relationships between different data sets. This enables linked records and data integrity.
5. **Schema Maps**: Visual representations of table relationships help administrators understand the data model and plan modifications.
6. **Table Rotation and Archiving**: For performance optimization, administrators can configure table rotation policies to manage large datasets and historical data.
7. **Dictionary Entries**: Each field in a table has a dictionary entry that defines its attributes, including maximum length, default values, and display characteristics.
Proper table administration ensures data integrity, optimal performance, and a well-organized database structure that supports business requirements effectively.
Tables and Table Administration in ServiceNow
Why Tables and Table Administration is Important
Tables are the foundational building blocks of the ServiceNow platform. Every piece of data stored in ServiceNow—incidents, users, configuration items, change requests—resides in tables. Understanding table administration is crucial for ServiceNow administrators because it enables you to customize the platform, manage data effectively, and extend functionality to meet organizational needs. For the CSA exam, this topic is essential as it tests your ability to configure and maintain the core data structures of ServiceNow.
What Are Tables in ServiceNow?
A table in ServiceNow is a collection of records organized into rows and columns, similar to a spreadsheet or database table. Each row represents a single record, and each column represents a field containing specific data attributes.
Key Table Concepts:
• Base Tables - Parent tables that other tables can extend from (e.g., Task table) • Extended Tables - Tables that inherit fields and functionality from a parent table (e.g., Incident extends Task) • Table Inheritance - Child tables automatically include all fields from parent tables • System Tables - Core tables provided by ServiceNow (prefixed with sys_) • Custom Tables - Tables created by administrators to meet specific business requirements
Understanding Table Structure
Every table in ServiceNow contains: • Fields (Columns) - Define the type of data stored • Records (Rows) - Individual entries of data • Sys_id - A unique 32-character identifier for each record • Dictionary - Metadata that defines table and field properties
How Table Administration Works
Accessing Table Administration: • Navigate to System Definition > Tables • Use the Application Navigator and type 'Tables' • Right-click on a form and select 'Configure > Table'
Creating a New Table: 1. Navigate to System Definition > Tables 2. Click 'New' 3. Define the table label and name 4. Choose whether to extend an existing table 5. Select the application scope 6. Configure additional options as needed 7. Save the record
Key Table Properties: • Label - User-friendly display name • Name - System name (automatically generated based on label) • Extends table - Parent table for inheritance • Application - The application scope the table belongs to • Extensible - Whether other tables can extend from this table • Live feed - Enables activity stream on records • Auto-number - Automatic number generation for records
Table Extensions and Inheritance
When a table extends another table: • All fields from the parent are inherited • Business rules and other logic may be inherited • Records can be queried from the parent table • The child table can have additional unique fields
Common Base Tables: • Task [task] - Parent for Incident, Problem, Change, etc. • CMDB [cmdb] - Parent for Configuration Items • User [sys_user] - Stores user records
Dictionary and Field Management
The Dictionary stores metadata about tables and fields. Key dictionary attributes include: • Field type (string, integer, reference, etc.) • Maximum length • Default values • Mandatory settings • Read-only configurations
Best Practices for Table Administration
• Always extend existing tables when possible rather than creating standalone tables • Use meaningful naming conventions • Document custom tables and their purposes • Consider performance implications when adding fields • Use appropriate field types for data being stored • Plan table relationships carefully
Exam Tips: Answering Questions on Tables and Table Administration
1. Know the Navigation Path Remember that tables are managed under System Definition > Tables. Questions often ask where to find specific configurations.
2. Understand Table Extension Be clear on how inheritance works. If a table extends Task, it will have all Task fields plus any additional fields defined on it.
3. Recognize Table Naming Conventions • Custom tables typically have prefixes like u_ or x_ • System tables start with sys_ • The table name is different from the table label
4. Remember Key Base Tables Know which tables extend Task (Incident, Problem, Change Request, Request, etc.) as this is frequently tested.
5. Dictionary vs. Table Understand that Dictionary entries control field-level configurations, while Table records control table-level settings.
6. Focus on Practical Scenarios Exam questions often present scenarios asking what happens when you create or modify tables. Think through the logical outcomes.
7. Auto-number Configuration Know that auto-number is configured at the table level and generates unique identifiers like INC0001234.
8. Scope Awareness Understand that tables belong to application scopes, which affects where they can be accessed and modified.
9. Read Questions Carefully Pay attention to whether questions ask about creating new tables versus modifying existing ones—the processes differ.
10. Elimination Strategy If unsure, eliminate answers that reference non-existent modules or incorrect navigation paths first.