🔍Tables in ServiceNow

What Are Tables in ServiceNow?

Tables are where all data lives in ServiceNow. From incidents to users to assets everything is stored in tables. They define data structure, relationships, and record behavior in the platform.

🧰Key Table Concepts You MUST Know:

1) Base Table //👉 The foundational table other tables inherit from. Example: Task.

2) Extended Table  //👉 A table that builds on another. Example: Incident extends Task.

3) Custom Table //👉 User-created tables for unique business needs.

4) Dictionary //👉 Controls fields, attributes, and relationships.

5) Schema Map //👉 Visual map of how tables relate.

Why Tables Are So Important?

They define how data is stored & retrieved
Extendable – you can build new modules on existing ones
Used everywhere – forms, lists, workflows, APIs.

🧠 Top 10 Interview Questions & Answers

1️⃣What is a table in ServiceNow?

A data storage structure containing records (like a database table).

2️⃣What is the Task table?

A core table extended by Incident, Change, Problem, etc.

3️⃣ What is table extension?

Inheriting fields and features from a parent table.

4️⃣What is the difference between global and scoped tables?

Global tables are accessible platform-wide; scopes are limited to an application.

5️⃣How do you view table relationships?

Use the Schema Map to see parent-child connections visually.

6️⃣ What is a dictionary entry?

Metadata defining a table’s fields, types, default values, and attributes.

7️⃣What is the difference between core and custom tables?

Core tables come with ServiceNow; customizations are user-created.

8️⃣ How do you create a custom table?

Go to Studio → Create Application File → Table.

9️⃣ What is table inheritance?

A child table inherits all fields of the parent and adds its own.

🔟Real-world example?

A 'Change Request' record contains all 'Task' fields + its own (risk, impact, etc.).