We have observed instances where the same knowledge article number is assigned to completely different knowledge articles, leading to data inconsistency and confusion.
We are currently evaluating approaches to identify such duplicates and implement corrective measures.
Could anyone please suggest:
- How can we effectively identify duplicate knowledge article numbers in ServiceNow (e.g., using scripts, reports, or queries)?
- What would be the best/feasible solution to resolve this issue, ensuring uniqueness and preventing such inconsistencies going forward?
Any recommended best practices or real-time use cases would be highly appreciated.
