
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 07:35 AM
I am preparing a large set of data to import into our CMDB and to test I am using a sub-set of about 25 records. When I use the transform map to create the records they are created on the alm_hardware table but the associated CI is not being auto-created as expected. I tried doing the reverse and imported the CIs but the assets were not auto-created as expected.
I know I have done this before without issues and cannot figure out what I am missing.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 08:45 AM
You are mapping u_model directly to model_id field, and you are not mapping model category at all. Both are required to create an asset correctly and create a resulting CI. This is the cause of your issue.
Model: Since there is no source script used here, and presumably the value of u_model is not a sys_id of a Model reference, this won't work. You need to provide a reference to a valid model. My recommendation would be to use a combination of u_manufacturer (if available) and u_model, and then use MakeAndModelJS script to automatically obtain or create a valid model reference on the fly. If you do not have u_manufacturer available in your data source, you will need to determine an appropriate method to supply a valid model reference, or else this will not work correctly, because it cannot determine what model to use.
Model Category: This is typically something that you will have to provide some customized logic for, depending on your data source. Like model, it has to be a reference (sys_id) to a model category. It's not a String field. So you will need to map the information from your data source to an appropriate model category in your system.
Please mark as helpful and as correct answer if this resolves your issue.
Paul
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 09:09 AM
That's what it was, while I pasted the wrong screenshot as I did have the model category in there. I changed the Model and Model Category entries to their respective sys_ids and the import worked as expected. thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 09:10 AM
Glad that worked out. Can you please mark my answer as Helpful and as Correct Answer? Thanks!
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 05:48 PM
Hello
I am facing the same issue. In my case I am importing the data(an excel file) to the alm_hardware but it is not creating CI's on the corresponding CI table which is based on the model category. I made sure the model category, model, manufacturer is mapped appropriately and as these fields are reference based, I made sure that ref tables have the data that wrt whatever I am importing.
The model category is OOB(computer) it has its ci class : cmdb_ci_computer and asset class: alm_hardware.
According to my understanding, if a record is created on either of the tables, should appear on the other if the model category is chosen right. The CI creation happens when I create a random 1 record manually with the same content that I am importing, but when I am bulk importing this data to the alm_hardware, the CI is not created.
Your Help will be really appreciated.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 08:42 AM
You may find something in the 'import log', 'transform history', or 'transform error' under 'system import sets > advanced' that could potentially indicate the cause, have you checked these? Typically when I run into import issues I find the cause listed there.