Importing data on alm_hardware and it is not creating records on the Cmdb side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2025 06:46 AM
I am importing data into the alm_hardware but it is not creating a ci on the cmdb_handheld_computing. I made sure that the model category "mobile devices" has ci class and asset class defined perfectly.
I am importing data into the alm_hardware, but it is not creating a ci in the cmdb_ci_handheld_computing table. I believe, if a model category has the ci class and asset class defined and while importing if we make sure that the model category field is mapped right, it should help the ci's to be created on the corresponding ci table.
What's happening here is, if I just import to the alm_hardware, without a config item field data, it is creating a config item name based on the model field automatically. and only the ones with unique ci name are appearing on the cmdb_ci_handheld_computing table.
Now, if I import the data with unique-configitem name to the alm_hardware, it is not creating a record on the cmdb_ci_handheld_computing table.
The models are already loaded in the cmdb_hardware_product_model table. I would like to know what is causing this and please help in making this make sense to me.
Hopeful that the following attachments might provide some better understanding over this issue.