- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 08:25 AM - edited 07-15-2024 08:32 AM
Why doesn't a table extended from configuration item show the columns that are on cmdb_ci like incident shows the task root columns?
I created u_is_this_real on cmdb_ci, but it doesn't show me that on any of the extended tables; they each show their own name respectively. However incident shows all the columns that are created on task as table = task.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 08:48 AM
@kimberlylp Incident and Configuration Item tables follow different table extension models. Incident table follows,
Table per hierarchy extension model where
Fields are derived from parent class:- Child classes derive fields from parent classes. For example, the Incident table derives fields from the Task table.
On the other hand cmdb_ci table follows Table per partition extension model where
Fields do not derive from parent class: - Child classes do not derive fields from parent classes. Instead each child class has its own list of fields. For example, the Base Configuration Item [cmdb], Configuration Item [cmdb_ci], and Hardware [cmdb_ci_hardware] tables all have their own field definitions.
I recommend reading this documentation https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/table-admini... to know more about the extension models and their behaviour in ServiceNow.
Please mark the response helpful and accepted solution if it manages to address your question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 08:48 AM
@kimberlylp Incident and Configuration Item tables follow different table extension models. Incident table follows,
Table per hierarchy extension model where
Fields are derived from parent class:- Child classes derive fields from parent classes. For example, the Incident table derives fields from the Task table.
On the other hand cmdb_ci table follows Table per partition extension model where
Fields do not derive from parent class: - Child classes do not derive fields from parent classes. Instead each child class has its own list of fields. For example, the Base Configuration Item [cmdb], Configuration Item [cmdb_ci], and Hardware [cmdb_ci_hardware] tables all have their own field definitions.
I recommend reading this documentation https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/table-admini... to know more about the extension models and their behaviour in ServiceNow.
Please mark the response helpful and accepted solution if it manages to address your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 10:24 AM
Thank you for the information.