Question

How to tag the duplicates of contact to the contact

Hello Community

My client have this requirement, where system will search for the duplicates on saving the contact. If duplicate records are found then system will save the contact and also  tag those duplicate records and send contact for higher management approval. Contact will be inactive at this stage. If approver approves the contact will be active and work normally. If approver rejects then record stays inactive.

 

I got the 'Id' of duplicate records from duplicate page by using 

DuplicateCollection = this.get("GridData").collection.keys;

I am unsure of how to tag these records to original contact. Similar kind of functionality is present in Leads (Similar Leads) detail. I am unable to find how they implemented.

Multiple contacts should be tagged with a singe contact. when linking with a detail what should be the detail column and master column. Please help me with this requirement. Also please suggest any other effecient way.

Like 0

Like

1 comments

Hello Nagaraju,

 

Yes, you can retrieve the collection of found duplicates using the approach you've mentioned, but you also need to use this collection somewhere, aren't you? And the problem here is that the record is created after clicking the "Save" button and all the client data from the "LocalDuplicatesPageV2" is removed after closing the page that is performed after saving the duplicate record.

 

Yes, you've correctly pointed that there is a functionality of similar leads on the lead edit page. All the logic of the detail (including calling the deduplication service) can be found in the LeadsSimilarSearchResultDetailV2 schema (we are interested in setSimilarLeadFilter, loadGridData and callDeduplicationLeadServiceMethod methods).

 

I was thinking on creating a detail that could load all the contact records on the contact edit page and then apply the filtration logic that could only display contacts with a similar name for example (this list of filtration rules can be also extended (via ESQ for example)). Because creating a separate deduplication service method for contacts will be a hard task and it will be easier to create a detail I've described.

 

Best regards,

Oscar

Show all comments