Avoid duplicate entries in the location table

[ravic]

Hello Community,

I am looking for you help to avoid the duplicates in the cmn_locations table. As all of you know Name, Street, City, State, Zip and Country are the key fields in the Location table but we are seeing some duplicates there. 

Suppose one street written like 'East Coast Street' and other user may write it like 'E Coast Street' so technically both of them are same but 2 records are there.

Pls share your thoughts how can we design a solution to avoid such kind of duplicates.

Thanks

#serviceNow "cmn_location

[Ankur Bawiskar]

@ravic 

it's part of data clean up that the admins should frequently check in location table.

Location table is usually loaded once and maintained over a period of time and requires manual intervention.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Hi @ravic 

Being a BPC, I can understand the pain you’re facing with duplicate data. The main reason is that many users are manually creating location records, and if there’s no integration in place, it can only be handled manually. Since there’s no direct way to stop this, it’s better to perform a data cleanup before loading the data manually.

You can also create a catalog item to add new locations into the Location table and place an approval flow for better control. Some restrictions can be applied at the name level, but applying them to other attributes is quite challenging, mate. This can be better managed by setting up a proper governance process in place.