difference between Base Table and Core table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2015 02:24 AM
What is the difference between Base Table and Core table ?
- 44,733 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2016 04:49 PM
The way I've always understood it is much the way you explained it, thus the way I have taught it to others. The way I break it down is like this:
- Core = Any table that exists by default in the baseline instance.
- Custom = Any table that is created by an Admin that does not exist in the baseline instance.
- Base Class = Any table that is a parent table (has children) [extended], but is not a child of any other table [doesn't extend or not extending].
- This pertains to any table, but think of it primarily in regards to newly created tables to help separate Core from Custom.
- Parent Class = Any table that has children tables [is extended by], but that is also the child of another table [extends].
- This pertains to any table, but think of it primarily in regards to newly created tables to help separate Core from Custom.
- Child Class = Any table that has a parent table [is extended from]. This pertains to any table, but think of it primarily in regards to newly created tables to help separate Core from Custom.
- Core Base = Any table that is installed by default in the baseline instance that is a parent class table without being the child of another. (Example: [task], [cmdb])
- Core Parent = Any table that is installed by default in the baseline instance that is a parent class table that also is a child of another. (Example: [cmdb_ci], [change_request])
- Core Child = Any table that is installed by default in the baseline instance that is the child of another table. (Example: [cmdb_ci_application])
Hope that helps. If not, we're all in trouble.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2016 01:04 AM
That's my understanding... however I can't find anything in the official documentation about it and my requests for clarification from the authoritative sources have still gone unanswered.
Unfortunately, I've had these questions from people who have sat the examination since it appears to come up as exam questions, and I've been unable to provide a truthful answer, only what my theory is!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-11-2016 08:36 PM
See if this helps:
"A table can "extend" another table. A table that extends another table is called a child class, and the table it extends is the parent class."
"If a table is extended, but itself is not an extended table, it is then called a base class."
Fuji and prior: Tables and Classes - ServiceNow Wiki
Geneva: Tables and classes
Helsinki: Tables and classes
"Task [task] table: The Task [task] table is one of the core tables provided in the base system."
Glossary of Terms: http://wiki.servicenow.com/index.php?title=Glossary_of_Terms#gsc.tab=0
Also, from the ServiceNow System Administration - Geneva book (doesn't apply to this because of the overall paragraph, but I believe it clears things up):
"Many tables are tracked in the base instance. The update_synch attribute is a Boolean that is set to true or false. Even though it is available for all tables, do not use on some core tables because more than one table can be involved in the data."
From those definition, much like some of the training material, it looks like they are making assumptions that people understand what "core" means given the context. I suppose there is another interpretation that could be "core" meaning one you use the most, but that wouldn't make since the ones you use the most aren't actually task or cmdb but rather the tables extending from them like Incident, Problem, etc.
In the Workflow Editor, they use the word "Core' as a tab that represents the activities, etc that are included in the system by default that are used to create the Workflows.
This is how I sorted it out. I could be wrong, but so far, the way I've taught it hasn't had any issues with certifications. Hope it helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2016 10:37 PM
Hello Arpit
Base Tables are those which doesn't have any parent like task, cmdb.
Core table is any table which is at root of your application
If you are working on Incident module than your core table will be Incident
while if you are working for your custom app then core table will be the table which is at root..
Base table may be a core table(as task table is base as well as core) ,but it is not necessary that core table is always to be a base table.
Regards'
Kirtesh
Plz mark as correct/helpful/like if you feel so;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2016 01:06 AM
kirtesh jailia wrote:
Core table is any table which is at root of your application
Where did you find this definition? Can you clarify what you mean by "root of your application"..? If I'm using the Self-Service application, what table will be the core one here?