Assets not being created from Service Graph integration

[David Casper]

We are utilizing a service graph connector to pull in devices into the CMDB. It uses IntegrationHub ETL and creates that CIs without issue. 

However, at first it would not create new models using the correct. They were being created using the hardware class rather and Facility or Industrial which is for IoT and OT devices. This was fixed by following this article: How to resolve 'Incorrect Model Class for Medical ... - ServiceNow Community and the key was using the 'Cleanse Hardware Model with Model Number Transform Operation'. 
After implementing that the assets are still not being created. If I go to the table directly and manually create a CI or create one through a background script the assets are created as expected. 

Has anyone run into this specific issue or any asset creation issue when bringing in CIs through a SG connector? 

Thanks

[Ashok Sasidhara]

Have you checked the following?

1. On each of the model categories, see whether 'Enforce CI verification' field is unchecked. If it is checked, assets won't be automatically created

2. On each of the models, check what is populated in the 'Asset tracking strategy' field. The default will be leave to category which means asset creation behavior will be based on the model category. If it is populated as 'Don't create assets', it will not create assets (this will override the model category behavior). If it is populated as 'Create consumable asset', it will create consumables.

[David Casper]

Thanks for the suggestions Ashok. I'm way passed that point. As I mentioned the assets get created without issue when using a background script or manually creating them. Right now I'm trying to figure out if there is a breakdown in a BR and if so...where.

[gk13]

Hi @David Casper did you found the a solution for your problem? I'm running into an similar issue. In my case the BR "Create Asset on insert" didn't trigger (condition of BR prevented it), because I had to provide a value in the IHUB ETL mapping for the asset field (dictionary overwrite was defined for that field). Removing the dictionary overwrite led to another error in the system log when running the IHUB ETL solution: Duplicate entry "xxxxx" for key "PRIMARY". The strange thing is that creating the CI via background script (using IRE functionality) works

[scottl]

Is there an answer to this, and why is SN dragging it's feet on an answer to this? This is fundamental to the entire concept of SG connectors populating the CMDB.