Content Comparison

This page contains documentation on analysis, proposed steps to de-dupe phone numbers in Alternate Channels (Account) objectwhere the phone number already exists in ‘Mobilephone’ filed on Contact object.

Approach:

Phone numbers linked to contact records were isolated and cleaned to remove -

• Any special characters, blank spaces etc.,

• +61 was replaced with 0

• 00s & 000s were replace with 0

• 00011 was replace with blank

Most recently created record of a unique phone number on each contact was considered ‘Primary Phone’ and any previous occurrence of the same number was considered ‘Duplicates’.

‘Primary Phone’ was used as an anchor to look up potential duplicates for each ‘Primary Phone’.

1. ‘Primary Phone’ created by mulesoft

2. ‘Primary Phone’ not created by mulesoft

Exclusions: Contact Type - ‘Student’ , Linked To - ‘Contact’ Object

Overarching Rule:
Given the Status of Primary Record is Former/Good:

For records that have been modified:

Given a TAP user modified any of the duplicate records and the last modified date of that record is the latest, the record with the latest last modified date will be retained.
For records that have never been modified:

If the cleaned phone data in Mobilephone field exist in Alternate Channel, then delete the Alternate Channel Phone record.