- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2017 07:05 AM
Hi All,
I have created one field under cmdb_ci table, will this extends to other child tables (like server & application) / should I need to create the field in each class.
If field extends to other child tables where i need to create that filed.
Kindly help....
Regards
Laxman
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2017 07:07 AM
HI Laxman,
Yes, if you create a field on a parent class (like cmdb_ci) that field is made available to all inherited tables. Be sure you need this on all tables so you don't run into any issues where it is changed on a table that does not need it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2017 06:20 AM
This is what the first thing that stuck me as bizarre when I was going through our Helsinki upgrade. I haven't understood till now why they added a extra layer and what was the benefit after introducing the abstraction.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2017 01:41 PM
I wonder if it had something to do with the asset application. Thoughts bsweetser?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2017 05:25 AM
No, this wasn't to do with the Asset application. The "re-parenting" to cmdb from cmdb_ci, as Kalai states, happened in Helsinki. My understanding is that this was done to better support non-IT types of Configuration Items, but I have not seen anything official explaining this.
That is really weird that you are seeing the fields twice. I just looked in an instanced of mine that I thought I had upgraded from pre-Helsinki releases and I do not see the fields on cmdb_ci any longer. It is possible I am mistaken as it has been a little while now. There should only be one copy of the fields remaining.
For Laxman's original question, the field should be placed on the highest level of the CMDB hierarchy that it makes sense. This makes it available automatically at lower levels. That is one of the benefits of the hierarchical structure.
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2017 05:42 AM
Thanks for the clarification Ben. I believe the instance I'm on started at H and now I'm up to J. We'll have to look in to the differences another time.
