How are Product Models created on import?

[peterraeves]

We had our CMDB in an SQL DB and wanted to import it in SN. In the "Model Categories" table, we set "Enforced Verification" to true for all classes that we will be importing, so no assets are created. We want to do this manually. Seeing we don't have "Product Models" yet, when we import CIs, the product model is automatically created, which is great. The problem is that, for Monitors for example, all Product Models seem to add both "Bundle" as category, as well as "Monitor", but we obviously only want the model category to be "Monitor". Also, I noticed that the product model's class is the generic one and not any specific. We obviously want to have "Hardware Models" in this case.

So what I'm trying to understand is the process from when the model id (eg: "HP LA2306" of a "Computer Display Monitor") enters the system, how it is transformed into an actual "Product Model" and how this can be configured, to create an Hardware Model, with "Monitor" as Model Category.

FYI: We removed the Monitor Model Category and re-added it, linked to the cmdb_ci_display_monitor class. OOTB, there was no class filled in, in the Monitor Model Category, which was very strange.

[Chuck Tomasi]

Hi Peter,

I'm taking a swing at this... This may help.

Model Categories - ServiceNow Wiki

[peterraeves]

Where does that page explain the automatic creation of Model Categories during transformation with Transform Maps?

[Deepa Srivastav]

There is a Business rule which automatically creates asset on ci insert ... 'create asset on insert'.. in that a function createAsset of script include assetandCI is called..in that you will find the mapping...

Regarding the existing model categories bundle hardware software... you can remove if you don't want them..

Hope it helps..

Installed with Asset Management - ServiceNow Wiki

Mark Correct if it solved your issue or hit Like and Helpful if you find my response worthy.

Thanks,
Deepa

[peterraeves · Accepted solution]

Not really . I was talking about the creation of product models, not assets.

One of ServiceNow's engineers just called me directly and he explained what was happening. It looks like Product Models are not created as expected, because there just isn't enough to go on, as the only thing we have is the Model's name. Therefore, they suggested to either manually create the models, before importing, or to create a separate Transform Map, to run before the other one, which will first set all Product Models. That way, we can specify how they should be set and how the fields should be filled in. The newly created Model in the first TM, could then be referenced in the second.