Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Updating Enterprise Model Categories

ayman_h
Kilo Sage

Hi,

We would like to use the Facility Hardware CI Class (cmdb_ci_facility_hardware) but noticed that OOTB there is a Model category that points to the Facility asset (sn_ent_facility_asset) class.

 

If we would like to use this CI Class, is the best practice to delete this OOTB Model Category and create a new one as I can't see a way to update the Asset class?

 

Regards,

Ayman

2 REPLIES 2

pavani_paluri
Tera Guru
Tera Guru

Hi @ayman_h 

 

No, best practice is not to delete the out-of-the-box (OOTB) Model Category. Instead, you should create a new Model Category that correctly maps to your desired Asset Class.

The Facility Hardware CI Class (cmdb_ci_facility_hardware) is designed to represent facility-related configuration items.
The OOTB Model Category you're referring to is likely mapped to the Facility Asset Class (sn_ent_facility_asset), which is used for asset tracking in the enterprise asset management plugin.

Do Not Delete OOTB Model Categories
- OOTB categories are used by ServiceNow internally and may be referenced by workflows or upgrades.
- Deleting them can cause issues during future upgrades or break existing functionality.


Create a New Model Category
- Go to Model Categories (cmdb_model_category).
- Click New and create a new category that:
- Points to the Facility Hardware CI Class (cmdb_ci_facility_hardware).
- Uses the correct Asset Class (if needed, create a new one under alm_asset or a custom class).
Map Your Models to the New Category
- When creating or updating models (cmdb_model), assign them to your new category.
- This ensures that any new CIs created from these models will use the correct CI and Asset classes.

 

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

 

Thanks @pavani_paluri

 

The issue is SN allows to have one Model category for each CI class.