How to disable inheritance for object type with child object types

[Antonia]

What is the best way to disable inheritance for an object type when there are already child object types?

Unfortunately, we made a “mistake” while setting up our asset database. We enabled attribute inheritance, but we no longer want that because the object types require different attributes. However, we already have several child object types, so we can't undo the inheritance. What's the best way to proceed now?
Would exporting and then re-importing be the only solution?

[Andrea Robbins]

Unfortunately exporting and re-importing is the only solution. However, just because there is inheritance, it doesn't mean that each object type cannot have their own set of attributes. In other words, you can have inheritance & attributes on only individual object types at the same time. There is likely some (if not all) attributes that can be inherited (Name, serial number, etc).

I would advise to do this:

1. Export all the objects to retain the values set to the attributes.

2. See which attributes ARE shared. There has to be at least 1-3.

3. Delete any attributes that you no longer want to be shared

4. Add back those attributes only on the object types you want the attributes to appear on.

5. Import using a CSV file the exported data to populate/update the attributes on the objects.

I would note too depending on the number of shared fields, a lot of people are fine with non-relevant fields appearing on all object types because in the future, if another object type needs to have it shared, it will be available if you keep the inheritance. What you want to avoid is having duplicate attributes with the same name, but different ids. As you grow and expand your CMDB, it is a hassle to have 5 Name attributes with different ids (especially for REST APIs).

Adding this too - if the objects are not inherited, you cannot see everything in the parent object type anymore, you have to click individually in each object type - like it doesn't roll up anymore. Another thing to keep in mind. :) 

Hope this is helpful!

Thanks,

Andrea

[Andrea Robbins]

For example, on this object type, some attributes are inherited, but I can add an attribute only on the virtual servers object type.

[Antonia]

Hi @Andrea Robbins,

thank you for your detailed response. Regarding your screenshot: We have a lot of attributes that have been inherited, and whenever we need a new attribute, it appears at the very bottom of the list. To fill it in, you have to scroll all the way down or search for it in the list.

[Antonia]

Also: We've linked objects in Jira fields. If I create new object types now, will those links disappear from the tickets? Is there any way to work around this?

[Andrea Robbins]

Sadly that is just how it is that you have to scroll down if you want to see the object type's non-inherited attributes as the inherited ones appear at the top. 

Yes, if you create new object types & objects, the asset fields on Jira tickets will be using the old ones which you would eventually delete. To get it to use the new objects, it could involve a lot of work. 

If you tried exporting it gives you this (this is a sample on my site)

Custom field (Reporter Information)

<workspaceId>:8142

where 8142 is the object id, which is going to change since you will create new objects.

I do not think it is worth the effort to change this just because of scrolling down to fill in an attribute.

You would have to create an automation rule to copy the Name of the object into a text field, then after the new object is created, create an automation to populate the real asset field. It is overly difficult to deal with this. I just created an automation similar to this, and trust me, it is not worth the effort.