Multisource: CI discovery source is populated with no entries in cmdb_multisource_data

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2023 04:48 AM - edited ‎06-07-2023 04:49 AM
Hi - I am working on a large CMDB with Multisource enabled. CIs are populated using different sources and in most cases the cmdb_multisource_data is properly updated with Discovery source containing the last contributing source.
However I also came across Configuration Items where the Discovery Source field is populated, but there are no corresponding entries in cmdb_multisource_data. This is not rare and one example is with Discovery source = ServiceNow.
I understand that if a source does not go via the IRE API to insert/update CIs, then cmdb_multisource_data cannot be updated, but I can point to scenarios where the source was processed via IntegrationHub ETL, SG Connector or ServiceNow Discovery. In this case it certainly went through IRE but I still see this problem.
Has anyone seen the same problem? Am I missing something?
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2023 04:32 AM
OK I'll reply to myself after further investigations. This happens when CIs have been inserted/updated by bypassing IRE.
Also I came across an edge case where if a CI has been reclassified after entries were written in cmdb_multisource_data, the old data will still refer to the former class.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2023 01:56 AM
Hello
I have this issue and I'm looking for solution to fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2025 04:58 PM
Yes, am having a similar issue where the CI is being updated but the 360 data does not reflect the data that updated the record, even thou everything is going through ETL

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 06:24 AM
I believe writing into the 360 table is a once-off thing, and the referential integrity is not maintained over time; that is if the CI has been changed, older entries in cmdb_multisource_data won't be updated.