Why are records from SCCM populating into cmdb_ci_computer table but not populating into cmdb_multisource_data?Issue This scenario applies to implementations of multisource CMDB in order to achieve field level data source precedence to prevent duplicate CI's that are being created from different data sources like SCCM and ServiceNow discovery. The system is unable to see records whose discovery_source "Importset" populated from SCCM transform map, in cmdb_multisource_data table even after enabling Multisource CMDBReleaseAllCauseThis limitation occurs when using SCCM 2012v2 legacy plugin integration. Note that SCCM 2012v2 is being deprecated and will no longer be supported beginning with the Tokyo release. ResolutionAny possible custom transform map being used with SCCM 2012v2 should call createOrUpdateCI*. If instead it is calling identifyCI(), this will only do identification and will not fully process the data payload into the CMDB. Therefore, data will not be populated into cmdb_multisource_data when passing through this processing path. Additionally, the population of cmdb_multisource_data is a feature of IRE (Identification and Reconciliation engine). As such, IRE must be used in order to both Identify and Reconcile the intended CI data into the CMDB. In order to achieve this, an appropriate IRE API call is needed to be used. Supported calls include createOrUpdateCI() or createOrUpdateCIEnhanced(). It is highly recommended to plan and migrate to Service Graph Connector for Microsoft SCCM (SG-SCCM) before migrating to Tokyo release. Service Graph connector for Microsoft SCCM is free for all customers and has a number of logical and performance benefits over the legacy plugin integrations (SCCM 2007, 2012v2, 2016).Related LinksThe KB article KB0744504 confirms Discovery Source(discovery_source) field is not populated with SCCM For more information about IRE, please visit our documentation page Identification and Reconciliation engine (IRE) Additional description of createOrUpdateCIEnhanced and createOrUpdateCI methods in IdentificationEngineScriptableApi - Global Developers reference also available in developers page IdentificationEngine