This is kind of continuation to our previous session where we understood about merging duplicate accounts.
But in this session we are going to learn about merging duplicate contacts.
So first of all why do we Mudge or duplicate context.
Basically as part of four data commencing right.
So then we handle data when we use other measures to find out the duplicate records in the system.
The next step would be to cleanse the data.
The first is analyzing and the second step is dancing.
So as part of cleansing then there are duplicate records.
Basically we have to clean up those duplicate records.
Right in that previous radio we understood how too much of a to duplicate icons on a similar fashion.
Let's understand how to much duplicate contacts so often there are multiple contacts existing in the
system basically as duplicates hold the much them the process.
I would say is pretty similar to how we do for icons and for understanding this concept I have created
some best data.
Let's consider this account my desk.
One two three.
So this is basically the most account but that's OK and here I have created three duplicate contacts.
If you see this account has got three duplicate contexts so go to the contacts related list of the accounts.
You should be seeing the duplicate contacts here and here.
You should be having this much context button so click on much contacts.
So basically you can much contacts belonging to them.
Same having the same primary account.
And he had in a similar fashion.
If you want to find the contacts if there are so many contacts associated to this icon then you're interested
in only some specific set of contacts who can use a search and you can pick only those contacts within
hours an idea we have only three contacts in total for the second.
So all the treacle contacts that are listed and choose the ones that you want too much.
So I have selected these three contacts all the contacts basically click on Next here in a similar fashion.
First we need to choose the master record so only the master records will remain in this system.
The other two records they will move to the recycle bin.
And similar to merging icons he had also those fields with contradictory values basically different
values conflicting values.
So that will be highlighted.
So in our scenario name and mailing address that feel this conflicting among the three records.
So that is why those visa highlighted and now as a data analyst you need to select which field to basically
be retained because a here I may choose this phone number or I may may even like or choose a mobile.
This one black right.
So basically you need to choose which is the value that needs to be retained.
So once you do that data mapping click much Okay all right.
Will affect and know that for the same account.
We have only one contact that is a.
Contact the other two records.
They are moved to the recycle bin.
So this is how you much context associated to an icon.
And why you we much context.
There are some considerations that we need to not first is the non must have context our move to the
recycling bin.
Yes.
Only the mustard contact reminds of the system.
The other context.
Moved to the recycle bin next is about the contact rules basically give all the contacts if they have
contact rules the non mustard contacts meaning of the records other than the master record those contact
rules they lose their status on the primary contact.
This is after the much and jacket of food is retained from the master record only.
This is actually similar to other account behavior.
Even an account.
It's the same.
So these are some of the considerations that we need to note while managing duplicate contexts.