CMDB Hardware Product Model NAME missing in some cases

Katie A
Mega Guru

Hello,

I have set up imports to our CMDB tables from both SCCM and Casper.

There is an issue with the model import. The the model "name" is not importing properly. In most cases, it works fine, but sometimes the "name" field is not importing, even though the source is present in the import table. Interestingly, in those cases, the "display name" is present and shows the correct name.

We are importing Models with a separate transform map that runs first, and then the second transform map imports the computer records.

Transform Map:

ITAM - SCCM Computer Identity Model     Order 100

ITAM - SCCM Computer Identity       Order 200

The source script on the Name field simply removes underscores and doesn't do anything else. The model import works most of the time, but there are a few hundred cases where it does not.

Steps to reproduce:

cmdb_hardware_product_model   >   name field is "empty" whereas display name shows the correct value in several records

1 ACCEPTED SOLUTION

Community Alums
Not applicable

kda617,


Per our phone discussion, the issue appears to have been with your Computer Identity imports. The Model information brought in with the Computer Identity was trying to match up with the Display name for the Model record, not the Name, which is what is contained in your import data.


To fix this, we:


  • identified what field should be used to identify the record (name)
  • set the Choice action to reject, so the entire computer record is rejected if there is not matching Model, which should not ever be the case because you are importing Model information first

Please let me know if this fixes this for you.


Ben


View solution in original post

2 REPLIES 2

Community Alums
Not applicable

kda617,


Per our phone discussion, the issue appears to have been with your Computer Identity imports. The Model information brought in with the Computer Identity was trying to match up with the Display name for the Model record, not the Name, which is what is contained in your import data.


To fix this, we:


  • identified what field should be used to identify the record (name)
  • set the Choice action to reject, so the entire computer record is rejected if there is not matching Model, which should not ever be the case because you are importing Model information first

Please let me know if this fixes this for you.


Ben


Ben, You are the BEST!!! The change worked. Thanks so much for taking time out of your day to help.