Currently we're making some changes, and we are trying to get rid of business_criticity.
We have an extension to modify functionalCI, and we are removing this field like so:
However, other classes that are children of functionalCI have definitions in the core datamodels that point to this field. So, in turn, other classes such as PhysicalDevice, ConnectableCI, and dozens of others, all get errors as they can't find the field Business Criticity:
Error: Unknown attribute business_criticity from class DBServer.
We have extensions for all these classes, and our current solution is to add <item id="business_criticity" _delta="delete_if_exists" /> to every presentation sub-category (details, list, search, default search) on our extensions. This is currently working, but it's a bit tedious, is there any other way to propagate the deletion across child classes?
Last edit: Jacques Dancause 2025-06-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jacques,
Combodo's customers do have access to a SaaS tool called ITSM Designer, which take care of this tedious aspect of standard field removal across sub-classes, but there is no easy solution when done through iTop extension...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey there!
Currently we're making some changes, and we are trying to get rid of
business_criticity
.We have an extension to modify functionalCI, and we are removing this field like so:
<field id="business_criticity" xsi:type="AttributeEnum" _delta="delete" />
However, other classes that are children of functionalCI have definitions in the core datamodels that point to this field. So, in turn, other classes such as PhysicalDevice, ConnectableCI, and dozens of others, all get errors as they can't find the field Business Criticity:
Error: Unknown attribute business_criticity from class DBServer.
We have extensions for all these classes, and our current solution is to add
<item id="business_criticity" _delta="delete_if_exists" />
to every presentation sub-category (details, list, search, default search) on our extensions. This is currently working, but it's a bit tedious, is there any other way to propagate the deletion across child classes?Last edit: Jacques Dancause 2025-06-04
Hi Jacques,
Combodo's customers do have access to a SaaS tool called ITSM Designer, which take care of this tedious aspect of standard field removal across sub-classes, but there is no easy solution when done through iTop extension...
Thank you for the help anyway, Vincent!