Disk Table Not Populated via SCCM Integration

[syed_but_not]

Hi, 

I've set up our SCCM integration and we've been pulling data for quite some time now. The CI data mostly looks good, however we noticed that a bunch of models were created without assets under the manufacturer (Standard Disk Drive), which I now realize are coming from the Disk data source. When I look at the robust transform for SCCM Disk, I see that it's mapped to the CMDB Disk table and that the relationship between the Disk and the CI is there as well, however this relationship isn't being established and our CMDB Disk table is empty. Does anyone know why this is happening? Are these supposed to be generated as models instead of disks? We haven't modified anything regarding Disk since setting up the integration

[Andrew_TND]

Hi @syed_but_not when the service graph connector is out of the box, yes it has some pre defined transformers in there, however these are there to start you off and wont have an impact if you decide to add any additional logic.

[syed_but_not · Accepted solution]

Hi @Andrew_TND , the issue ended up being a duplicate "Contains::Contained by" relationship in our cmdb_rel_type table that was preventing the Disk import from working as it should have OOB.

[AJ-TechTrek]

Hi @syed_but_not 

Please check the Disk related Import set are running or not.

https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/integrate/cmdb/referenc...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/