Resolve De-Duplicate Tasks made from the CMDB Health jobs running

galaxypwm
Kilo Explorer

Hi,

My boss wants me to find out how to resolve the De-Duplicate Tasks that are created whenever the CMDB Health job runs and detects duplicate CIs. I need to know how to resolve the tasks without deleting any of the CIs even if they are duplicates. Is there a way to do this without deleting anything?

Paul

7 REPLIES 7

galaxypwm
Kilo Explorer

To Clarify here is the link to the documentation that talks about resolving de-duplicate tasks. At the bottom it suggests to delete or inactivate CI's that are duplicates, but there is not a field that we have been able to find that has the option of setting a CI to active or inactive (active = false).



Here is the link to the doc: Resolve de-duplication tasks



How can we resolve the de-duplication tasks without deleting any of the duplicate CI's?



Paul


Hi Paul



Were you able to figure this out? My challenge is that even if I delete one of the CIs, and mark the task as Close Complete, one of the CIs still keep showing as a duplicate in the Health Dashboard. I mark the CMDB Health Check Result record with Active = false, run the duplicate check scheduled job and it comes back again. Only this time, there is just one CI in the de-duplication task and I cannot seem to get rid of that. Any suggestions?


Paul was my summer intern so helping with an update.   Response from HI support:   De-duplication tasks will lead to some update on the CI via user intervention.


1. remove the record.


2. archive the record.


3. No action. Keep the record and know that no updates to the record will be made since the source field value for the duplicate record is set to "Duplicate".



I don't like the functionality of the product.   To your point it should be:


- Mark one of the duplicates (inactive).   Unsure why there is not an "active" field on the CI tables.   It would be so easy to active = false.


- Have the duplication activity of the health dashboard check only "active" CIs for duplications only.


Thanks Michael, appreciate the update. There is a field available on CIs titled operational_status. If you mark this as non-operational, the CI is ignored by


duplication checks. Please see the following post from Richard



https://community.servicenow.com/community/blogs/blog/2017/07/26/duplicate-configuration-items-in-th...



The fact that Duplicate resolution is not well documented if a bit frustrating at times though.



Manish