We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Removing custom model category from hardware models

Asmita7
Tera Expert

6 hours ago

Hi friends,

I had a custom class (desktop class) which is child of Computer (cmdb_ci_computer). This custom class in in sync with hardware(alm_hardware) through a custom model category Desktops.

now, we want to move to OOTB configurations. We want to delete this sync between Desktops class and hardware class. We want to move all the records from custom class to Computer class going forward.

1. When I try to change the Model category on hardware model to Computer from Desktops, I can change it but It again adds back the old model  category i.e. Desktop any  of the related records is updated.

Asmita7_0-1783950344796.png

How to change the model category for hardware models from Desktop(Custom) to Computer (OOB)

 

2. I need to reclassify the records from Desktop (CI class) to it's parent Computer class without loosing it's asset side data and attributes?

 

Please help.

Thank you in advance.

Asmi

 

 

 

0 Helpfuls
  • 64 Views
1 REPLY 1

pavani_paluri
Kilo Sage

6 hours ago

Hi @Asmita7 ,

 

It sounds like the custom Desktop model category is still driving the synchronization between alm_hardware and your custom CI class. That's likely why the Hardware Model keeps reverting back to Desktop whenever a related record is updated.

 

For point #1, I'd recommend checking the Model Category mappings and any custom Business Rules, Flows, Script Includes, or Fix Scripts that reference the custom Desktop class/model category. In many implementations, the model category is automatically recalculated based on the CI class, so unless that mapping/custom logic is removed, the value may continue to revert.

 

For point #2, since your custom Desktop class is a child of cmdb_ci_computer, the safest approach is to use the CI Reclassification process to move records from the custom class to cmdb_ci_computer rather than directly updating sys_class_name. Reclassification typically preserves the CI record, relationships, asset association, and inherited attributes while changing the class.

 

My suggested approach would be:

  • Stop creating new records in the custom Desktop class.
  • Identify and remove the logic that is forcing the Desktop model category.
  • Test reclassification on a small set of CIs from the custom Desktop class to cmdb_ci_computer.
  • Validate that the linked Asset records, relationships, and discovery updates remain intact.
  • Perform the bulk reclassification.
  • Update the Hardware Models to use the OOB Computer model category and retire the custom Desktop model category once everything is validated.

Also, make sure to take a backup/export of the impacted CI, Asset, and relationship tables before performing the bulk migration.

 

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P
0 Helpfuls