Reject all the duplicate CI data available in excel while upload
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2024 07:14 AM
Hi All,
I have a problem statement where the ask is that if there are 'n' duplicate entries available in excel based on certain unique key, system should not even take the first entry, it should reject all the duplicate entries as available in the excel i.e. if i upload an excel where for same serial number 5 CIs are available then all the CIs gets ignored. Please let me know if this can be done.
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 08:26 AM
HI @Suraj Saurabh1 ,
For that, You can use the Coleace field to map the Unique attribute based on that CI will be Updated.
Also you can also write the on before or after transform Script based the whatever conation you required.
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/
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 11:25 PM
You might be better off scrubbing that data in Excel before uploading it to ServiceNow.
I would suggest you also look in to utilizing the IRE in your transform map. You find out more below:
CMDBTransformUtil - Global (servicenow.com)
CMDBTransformUtil Usage in Transform Maps - ServiceNow Community
Hope this helps
//Casper
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 12:36 AM
A better approach would be to educate the users to do CMDB data imports only through Integration Hub ETL as it will consider the identification rules defined for each CI class while populating the data. Also make sure to restrict the permissions for data import to each CI class only to a pre-defined set of limited audience like configuration managers, configuration analysts, CI class owners, BAU teams etc.
The 2 points mentioned above are very important to reduce the possibility of bad data getting populated in the CMDB.
Finally, to address the specific point in your query, it is also important to educate the people who can load CMDB data to ensure that they clean up the data in excel file itself before doing the manual data import.