Placing a cmdb_ci table field to all related forms
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2016 10:29 PM
Hi Friends,
Can somebody please share your experience on below- I have a new field in cmdb_ci table. Now i need to place this new field on all the FORMS of different classes in relation to cmdb_ci e.g. Business Applications, Servers, Network etc.
Thanks in advice!
Nishant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2016 11:31 PM
Hi Nishant,
You can do that by creating the field in cmdb_ci table and then configuring the form layout or the list layout of the classes in relation to cmdb_ci e.g. Business Applications, Servers, Network etc.
see the example which I did for server forms- I created a field named test and then pulled on to the form layout
pull the field from available to selected-

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2016 11:53 PM
After Helsinki, I am not sure if you should add such fields to cmdb_ci or the cmdb table.
bsweetser What would be the best practice now since there is another base table involved?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2016 12:03 AM
I have seen a lots of things have changed in cmdb from the helsinki release , asset CI synchronizing has been set in mapping tables instead of script includes.
Yes, I would like to know the best practices followed for adding a field to the parent table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2016 08:11 AM
As with any attribute when extending, I would look at the appropriate level in the structure for the attribute. If it is something you want to be available to all Configuration Items, then use the cmdb table now.