Assets not auto-created with a new CI

[Steve Brown1]

Hi Community,

I have found about 160 Configuration Items that do not have a corresponding Asset record.   The CI's were imported over a year ago before we went live and they have only come to light now following a review of the CI's that were missing data in the ASSET Field on the CI record.   I'd like to think I did not uncheck the 'Run Business Rule' on the 'Create Transform Map' page before running the import!

I have tried changing the BR 'Create Asset on insert' from OOTB to the below and then running an import to update the Asset Field with the relevant information.

• When - After
• Update - Checked

I also tried using the 'Create asset on model change' BR and changing the Model on one of the CIs to no avail.

Each Asset record is read only.

The majority of the CI's have already been used to log Incident's so I can't delete the CI's and run the import again.

Has anyone come across this issue before and been able to resolve it so the Assets are created after the CI was created?

Many thanks

Steve

[blazye44]

Stephen,

Navigate to the ALM_Hardware table and create the Asset you need which can be bulk uploaded with all the required Attribute information. The business rule may create base CI records and may have to be disabled before you upload the records or delete the CI records created. Link the CI's to the Asset records created. I would start with a handful in a Dev instance to make sure you don't encounter any other issues.

Eddie

*Please mark Helpful, Like, or Correct Answer if applicable*

[ggarcia1]

I know this is an old post, but for anyone who ends up here, there are a few things to keep in mind:

If your imported CI has a Model, then you'll have to check the Model Category for that Model to ensure we've instructed ServiceNow to create assets for this model.

If there is not a Model Category on the Model, then you need to populate an appropriate Model Category on the Model for those CIs, then assets will be born at that time.

If your Model has a Model Category that does not map to your CI class (this is easy to overlook on imports of network devices or servers), then you'd have to add the appropriate Model Category and temporarily modify the Create Asset on Insert business rule with the Update flag checked, then perform any sort of update on each of those CI's, which will now trigger the business rule and produce an asset (then don't forget to uncheck the Update flag on the business rule again).

Since we're talking about importing, it's wholly possible that the "Run business rules" flag was unchecked on import (although the OP says that's not his case, it might be yours), then you'd likely only have to set the Update flag on the Create Asset on Insert business rule and make an update.

Each of these scenarios preserves your existing CI and gives you a fresh asset to complete the picture.

Practically all of this can be inverted for Assets without CIs using the companion business rule: Create CI on Insert.

I hope this helps anyone in the future.