- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2022 10:49 PM
Hi All,
I am populating CI using import set table I want to check if record is already present and update the record I enabled 'coalesce' it was good but I need to achieve this functionality using IRE so I used below script
Still it is creating duplicate record in target table , can someone please help if I am missing something.
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 06:25 AM
As others have noted, you're most likely missing an identification rule or mapping the wrong data into a field (so as not to cause a match). You can enable debugVerbose logging and check out what's going on in the process to confirm.
Properties for Identification and Reconciliation (servicenow.com)
In your script, it would also be a good idea to set a Discovery Source to make things easier to understand in the logs:
cmdbUtilIRE.setDiscoverySource([source name]);
If you haven't already, you'll need to register the Discovery Source first, though. You can do that in a fix script:
var sourceName = “[source name]”,
dsUtil = new global.CMDBDataSourceUtil();
dsUtil.addDataSource(sourceName);
Looking at your initial post, it should be a given, but we ought to confirm...your Import Set's target table is in the CMDB, correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2022 11:20 PM
Kindly Check that identification rules are rightly configured on your target table and make sure all Coalesce fields are set to false.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 01:37 AM
IRE will effectively ignore the coalesce you have set in your transform. You need to check the identification rules for the CI class you are targetting, that will likely be why you are seeing duplicates.
Hope this helps,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2022 06:25 AM
As others have noted, you're most likely missing an identification rule or mapping the wrong data into a field (so as not to cause a match). You can enable debugVerbose logging and check out what's going on in the process to confirm.
Properties for Identification and Reconciliation (servicenow.com)
In your script, it would also be a good idea to set a Discovery Source to make things easier to understand in the logs:
cmdbUtilIRE.setDiscoverySource([source name]);
If you haven't already, you'll need to register the Discovery Source first, though. You can do that in a fix script:
var sourceName = “[source name]”,
dsUtil = new global.CMDBDataSourceUtil();
dsUtil.addDataSource(sourceName);
Looking at your initial post, it should be a given, but we ought to confirm...your Import Set's target table is in the CMDB, correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2022 02:39 AM
I specified the dataSource and CI Identifier with correct attributes ..it is now working as expected..Thanks much