Configure multiple model categories in the Asset

[mugi-san]

Hello, everyone.

You can set multiple model categories for a single CMDB model. As stated in the documentation, it is possible to automatically create an CI when a Asset created that CMDB model is discovered.

However, I couldn't find information on which model category takes precedence when multiple categories are configured. Specifically, when an CI is automatically created when asset created, which "CI-to-Asset Class" mapping is used among the multiple options?

Since model categories can have parent-child relationships, it's unclear which relationship the system focuses on and which candidate is prioritized. Does anyone have more information or insights on this logic?

cf.

https://www.servicenow.com/community/cmdb-forum/configure-multiple-model-categories-in-the-cmdb-mode...

[Laveena-Agarwal]

Hi @mugi-san 

ServiceNow doesn't allow multiple model categories for particular CI Class.

I have tried to create new category for CI Class "AIX server" with different Asset Class, it throws an error.

(PFA)

[Vishnu-K]

Hi @mugi-san ,

Yes, that’s correct  a single model can be associated with multiple model categories.
However, when creating an asset, the Model Category field is mandatory along with the Model. The CI that gets created during asset creation is determined strictly by the model category selected at that time.

Because of this, there’s no concept of precedence between model categories the system simply follows the category explicitly chosen while creating the asset.

If this clarification helps, please feel free to mark it as helpful.

[mugi-san · Accepted solution]

Thanks, Everyone.

I created the model category shown below and configured the model to allow it to reference multiple CIs.

I then verified this in the PDI.

When creating a CI, the behavior works as described in my previous post.

However, when creating an Asset, you are required to select a single Model Category.

As shown below, it appears that when an Asset is created, the CI is only generated automatically if a Model Category directly linked to a CI is selected. Similar to my previous CI creation tests, my PDI verification suggests that the Parent Category setting of a Model Category does not contribute to the automatic CI generation logic during Asset creation.

regards.