I am working on an application in the CSM and we are creating Contacts (vs Consumers). I thought that the system was set up out of the box to prevent duplication of callers if a caller should call back, but it appears to not do so. I am looking for the best way to establishing a combination key for the table to help lock that down. Is there an easy way through a setting or through code to implement this? Thank you in advance for any assistance you may be able to provide.
Creating a unique index is one way that doesn't require any code implementation, but you need to make sure you don't have any duplicates or clean them if they exist before the index creation, otherwise index will fail.
