Importing Assets to existing hardware model

[Sam Kinney]

I have a question and it's probably easy, but I am overlooking something.  I am using the hardware asset template to upload assets to our stockrooms. When I do this it is not correlating the asset with the hardware model.  From what I see it is generating a generic hardware model.  "ThinkPad T590" without a manufacturer or category.  The model doesn't actually exist in the models table.  It is not adding the asset to the ThinkPad T590 model in production that was created manually.  What am I missing?

[DirkRedeker]

Hi

How are you referencing your model in the import file?

By display name?

BR Dirk

[Sam Kinney]

Display Name Yes.  I use a normalization to transform the 20N5xxxxx model name to the ThinkPad T590.  I am referencing it as ThinkPad T590.

[DirkRedeker]

Hi Sam

Did you solve your issue, or do you need some more assistance?

BR

Dirk

[Mitch McCain]

Hi Sam--

As Dirk mentioned, you'll want to verify your coalescing on display name. If you allow inserts then verify the choice action for the field within the transform map is set to create. My preference is to set to ignore and create hardware models separately from a HW import template. This can be done manually or through another HW model import template.

It is best to match the discovered hardware model from CMDB so the CI and asset records are properly mapped. If the same model isn't used then look out for duplicate serial numbers with different models. When coalesced on an existing HW model then the manufacturer and category will be populated with respective assets linked. If the model isn't found then the system places it in the cmdb_model_list table(instead of cmdb_hardware_product_model) without the underlying attributes which is what you've experienced. 

Best,

Mitch