Hi @SIVASANKARIS
This behavior is actually expected, even though the wording in the Deduplication Template UI makes it a bit confusing.
A few key points that helped clarify this for me:
1. How the template filter really works
The “Condition to filter CIs from the template class” is evaluated at the CI level, not at the deduplication task level.
If a deduplication task contains multiple CIs and at least one CI matches the filter, the entire task gets assigned to the template.
So if a task contains:
CI 1 – Company = Sony
CI 2 – Company = some other company
The task will still be picked up because one CI satisfies the condition. This is by design.
2. Dot-walking on Company is unreliable here
Using conditions like Company > Name is Sony does not consistently work in deduplication templates. The filter engine does not reliably honor dot-walked conditions in this context.
The safer and supported approach is:
Company is Sony (using the reference field, selected via the lookup, not typed as text)
3. Template class matters
The filter only applies to the Template Class (for example, Windows Server).
If a deduplication task contains CIs from multiple classes, only the CIs belonging to the template class are evaluated for the condition.
4. Existing tasks are not reprocessed automatically
Templates do not retroactively update already-created deduplication tasks.
To see changes take effect, the tasks need to be re-evaluated or the deduplication process needs to be re-run.
*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
