How to Create a CI from an existing asset?

Teri Bobst · ‎03-07-2017

Hi Community, we had a data import during our Asset implementation that created the Asset records without creating the corresponding CI's. This was related to bad mapping on the model information and has since been corrected so all new imports work as intended.

My question - how can I go back to the 100 or so asset records that do not have CI's and force the creation of the CI? Is there a simple way to do this, or would it be best for me to just delete the assets and re-import all of them?

Thanks,

Teri

Alikutty A · ‎03-07-2017

Hi,

I believe you have to delete and reload the assets.

There are basically 2 business rules that synchronizes data in the alm_asset and the related CI table

Create CI on insert

Update CI fields on change

Thanks

PS: Hit like, Helpful or Correct depending on the impact of the response

Teri Bobst · ‎03-21-2017

Ok, so I have tried just deleting the Asset (without a CI) but leaving the CI (created through discovery). However, when the asset is recreated, it creates a new CI. So now instead of an Asset without a CI, I have two CI's with the same serial number!

I can't delete the CI's or any historical data such as incidents, changes, etc will be lost.

Is there a way to link an existing asset with an existing CI?

angeliccharm · ‎03-22-2017

Hi Teri,

I'm running your last response by my tech team and will get back to you as quickly as possible. In the meantime, have you garnered assistance from a ServiceNow implementation partner? Since we are such a partner, our expertise takes customers like you from clobbering discovery "gremlins" and the like, to resolving the business issues you're currently facing by implementing your ITSM and ITOM modules rapidly with our QuickStart solutions.

Let's schedule a quick call to have a chat about your current SNOW implementation status. You can reach me at lisa@configuretek.com.

angeliccharm · ‎03-12-2017

Hey Teri,

We concur with Alikutty. It will save time and reduce the risk considerably of having inaccurate data held in the CI table.