Loading assets. CI's that are created are not stored in the correct area and are basically blank

[Stephen Updike]

Hello,  We are bulk loading some IT assets.  We built 2 and appropriated 3 CI Classes under Network Gear.  We built our corresponding Model Categories which are linked to the matching CI classes.  We bulk loaded our models.  The models look fine and are connected to the correct Model Category.  We loaded our assets.  The asset records look good.  They are correctly populated and are connected to the correct Model and Model Category and you can link to them from the asset.  The CI's were created, but they were all stored attached to the very top level of the CI Class hierarchy and they appear to be mostly blank.  You can link to them from the asset, but the asset screen that is displayed is very rudimentary and contains 7 data fields and no tabs.  As our model Id and Model Category were correctly stored in the asset and the links correctly built, why was the CI not created under the corresponding CI Class?  Why was common data in our asset load not stored in the CI record?  Why do we see such a limited CI screen.  Any shoves, gentle or rough, in the correct direction will be greatly appreciated.     

[Ashok Sasidhara]

It is better to create CIs first for all the assets which are already operational as CIs. Also you can control the asset creation behavior at the following 2 levels:

1. Model categories: Check the 'Enforce CI verification' field to prevent asset creation for CIs of that model category. It is unchecked by default and so assets will be created for new CIs of a model category except when there is an override on the model record.

2. Models: There is an 'Asset tracking strategy' field which is populated as 'Leave to category' by default (i.e. Asset creation behavior will be based on how it is configured in the model category). This can be changed to 'Don't create assets' (if you do not want to create an asset for that model. E.g. When that model is not used in the organization) or 'Create consumable assets' (if the organization wants to treat that model as a consumable)

For Asset-CI fields sync, look at the 3 asset-CI field mapping modules indicated in the attached screenshot.

If you are still facing issues, also check whether the following components have got customized:

'Create CI on Insert' business rule

'Create Asset on Insert' business rule

'AssetAndCISynchronizer' script include