SCCM Integration failing after promotion

[Cal Riley]

Experts - 

We have setup and successfully configured a working SCCM integration in our DEV instance. We recently promoted it to our test instance and the connection seems to still be working as it successfully grabs the data and loads it into the import set table for Computer Identity. However it never completes the transformation and so it never updates/inserts any records into the actual target tables (cmdb_ci_comptuter etc...). On top of this it is taking the scheduled job 8+ hours to try and run. Not sure what went wrong with the promotion or configuration of this in the test instance, as it is still working normally in the DEV instance. The only difference I am seeing is the sys_object_source table does not seem to be getting populated in the test instance - which to my understanding seems to store the resource id/target id relationship of where to map the data. Is there a way I can find out why this table is not being populated or find out why the transform job is not completing even though the data is imported and ready to go. 

Please let me know of anything you can think of to help debug this!

[Cal Riley · Accepted solution]

Thanks for the article Rahul, as I responded to someone else, it seemed the partial_payload and sys_object_source not being populated as expected was the symptom of the problem. So it was very much related to what is in the article. It seemed my problem originated from this system property being toggled glide.required.attribute.enabled. This caused the IRE to malfunction and just populate the partial_payload tables instead of the sys_object_source.