Using a template to bulk remediate de-duplication tasks

[Sequita B]

When I run a template for IP Router the only de-duplication tasks that were remediated were the tasks that had IP Router CI only.  The other tasks that had IP Router along with 1 or 2 other CIs were skipped over due to "Skipped adding de-duplication task(s) to template ######## because the template-task class hierarchy does not match".

How do I bulk remediate de-duplication tasks that have multiple CIs in them?

[AJ-TechTrek]

Hi @Sequita B ,'

I never suggest to use the remediate the de-duplicate task using the bulk because it will meshed up the data.

As de-duplicate task created based on some unique attribute in both class CI, till you are not doing manually you are not able to find the which one is correct CI and where you need merge the CI.

if you feel One ci is manually created in same Class or parent class and one is discovered then only you can go for bulk but this is also exceptional case.

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

[AbhishekUpasani]

I think the skipped message pretty much says it all. You are trying to add a task created for class that does not match the template class.

For example, it the template was created for linux server, you cannot add a task created for computer to the template. The main reason being that there are certain fields in linux server which are not there in computer. So these fields can be selected as template options for selecting main CI, merging attributes, updating duplicate CIs etc. and might not work with computer tasks.

However, the vice versa is possible. You can create a computer template and add linux server tasks to it (because all computer attributes are available in linux server). 

I your case, looks like the there are some tasks with different classes which might not work with the template if remediated. As a fail safe measure, we block adding these tasks up front. 

A possible workaround could be to create the template at a higher class level in the hierarchy.