How to modify model category

[Ahmet Damli]

According to https://docs.servicenow.com/bundle/tokyo-it-asset-management/page/product/product-catalog/task/t_Edi... it should be possible to modify existing model categories.

As a example I would like to change this category  "Tablets" to apply on CI-Class "cmdb_ci_pc_hardware", but i can not update the CI-Class. So do i need to DELETE this Category first and then create it new?

It seems that some attributes like CI-Class and Asset-Class can not be modified after creation of a category. Is this correct?

[Scott Halverson]

That is correct, the CI class and Asset class of a model category can be set only at creation time.  This is due to the intentional cleanup required of existing CIs/Assets needed as part of making this change.  Alternatively you can temporarily inactivate the field level acls restricting the updating of the record, or as you called out delete the record and create a new model category.

[Alec Hanson]

Hi @Scott Halverson , I am struggling with the fact that Mobile Device as a category is like this OOTB but the Intune ServiceGraph connector loads mobiles into the CMDB, so we would end up with 1 CI and 1 Asset not linked. Intune Mobile Device CI Class & Model Category lin... - ServiceNow Community

I was hoping to find a solution as part of the SG Intune connector as this must ahead to anyone who uses it. I also have assets already in the Mobile Device category, but not deployed Intune yet.

[DavidWallace1]

This is a known issue - the intune connector has hard coded one category, and the one that comes with HAM is different and doesn't have any mapping to a CI class either ootb. Frustrating.

What we did was to create a new model category in HAM and map that to the asset class that is populated by the InTune connector. This is of course more tricky when you aren't starting fresh and have existing assets in the model that you wanted intune to populate!

[Ahmet Damli]

thank you @Scott Halverson . I just want to be sure, not to have negative impacts later on. I remember,  that we delete some cmdb-relationship types, which we figured out later, it was not a good idea (and we had to recreate with same sys-ids).

So: As right now we have many categories 141 (most of them OOB), i can delete as example all those categories, where we even do not use the corresponding CI-Class (see screenshot below), and just create it later (if we really would need), correct?

Is this best practice or is there another way to "hide" the "unused" modelcategories?