field cmdb_ci table.

[laxmanboddu]

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

[Chuck Tomasi · Accepted solution]

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.

[Chuck Tomasi]

HI Laxman,

Let me know if you are blocked on this.

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thank you

[Kalaiarasan Pus]

Chuck, quick question. Is there any guide lines on deciding when to create fields on cmdb and when on cmdb_ci table?

[Chuck Tomasi]

Good question Kalai. I think this could turn in to a learning opportunity for a few people (including me.) Of course, the Technical Best Practices page tell us that you only want to create a field at a parent table when it is needed across several sub classes.

The schema map indicates that cmdb_ci is extended from cmdb

Here's the crazy part I don't understand... when I look at the dictionary for these two tables, they have a lot of the same fields. Why would cmdb_ci want to replicate fields that are already in cmdb?