So this session is basically the continuation of the previous session in the previous session.
We understood about the significance of duplicate management and how we can effectively use that to
have duplicates and control.
So in that we understood about matching rules how to create matching rules and how to activate matching
rules.
So as a continuation of that the matching rules that we created we need to use them in other duplicate
tools so that the duplicate criteria comes into effect and began half were duplicates in control.
Perfect.
So in this session what we are going to do this.
We are going to create duplicate rules using the matching rules that we already created.
So let's jump into our sales files and have a look at ah this is the matching rule that we already created
and this matching group we created for the instructor custom object the matching rules.
The instructor name is exact.
And the instructor position is exact.
Then the matching criteria is satisfied.
So it means two records with the same name and same position will be considered as duplicates.
Perfect.
So this is the matching route.
Now let's create ever duplicate rules.
So for creating duplicate rules go to set up go for duplicate rules
and here we know there are already standard duplicate rules.
Now let's create ever custom duplicate tool.
So create a custom duplicate to pick the object and in our scenario the object is instructor to instruct
or object
given the details give the ruling description I've given the rule name and I've added a description
but give a better description injury on time and the next is the record level security so that I call
the security they have two options that is to enforce the sharing rules or to bypass the shifting rules.
So what does this say for example I'm a user I'm creating an instructor record in the system.
All right.
And then I try to create an instructor of record that is already under the record with the same details.
All right.
So just consider this scenario but as a user I do not have access to the original card that does existing
in the system.
All right so in this scenario if Ian enforce sharing rules is checked then the matching rule will only
consider those records which I have access to.
Meaning it will not consider the record which is already existing in the system because I do not have
access to that record.
So that is the meaning of Ian full shedding rules and when it lists down the duplicate records existing
in the system in the game list only those records of which I have access to but if I choose bypass shouting
rules it will ignore those and rules and it will check against all the records that is existing in this
system.
However when it is alerting me each will only list down the records which I have access to.
All right so that is a difference so when I'm creating a record and if there are 400 duplicates in the
system so you influence sharing rules will check only against those records which you have access to
and it could also list don't only those records which you have access to bypass shred and rules will
check against all the records irrespective of the access level.
However when it is listing no records it is don't only those records which you have access to.
So that is a difference.
And depending upon your requirements you can choose the option accordingly so here let me say by best
sharing rules and then the actions so then the matching criteria is satisfied.
And if the system finds duplicates we need to set like what has to happen on duplicates so when duplicate
records are found what has to happen.
So that is what we we find another duplicate tool.
So say for example a duplicate record is already existing and now we create another record.
So what should we do.
Should we allow the user to create another record or should we block the user from creating their record
so then we say bloc does just blocking the user.
Then we say allow.
We are still given options should we alert the user.
So I learned to use it.
Meaning then I tried to create the second a duplicate record meaning the old generic record is already
there.
I'm trying to create a duplicate record so when I'm trying to create the second record if I choose this
option I load the system would say hey this record is already existing in the system so do you want
to use that record.
So the system will alert me.
What did you know record it you give the details of the original record and actually alert me that the
details I need to also report on that so that does these options that again depending upon the business
tonight and you can choose these options accordingly.
In my scenario let me say block do not allow the user to create a new records and actions on edit.
So here let me say allow and then let me stay alert and report and I let TEXT ALERT TEXT ME given appropriate
text.
Let me say potential duplicate record fault.
All right.
And now we need to define the matching.
So combat instructor record would instruct us and the matching rules matching flight instructors.
That is a custom matching rule that we create to all right.
So this is one matching rule.
Similarly we can add up to three matching rules for duplicate tool.
All right.
However one matching rule can have only one object meaning like one object can have only one match.
Though we can have three match rules.
We can't have three matching rules of the same object.
All right.
So one object can have only one matching.
But we have we can have up to three matching rules in a duplicate tool so that part over next coming
to conditions.
So conditions meaning should all the instructor records do they fall in that criteria or do you want
to specify some conditions.
Your record must meet flaws to run for example saying when I create an instructor record with some specific
type or with some specific location only in those scenarios and under duplicate tool but not for other
scenarios like that.
So if you want only some specific records who run the duplicate too then we can specify that condition.
Otherwise just leave it blank.
Perfect.
So now we have understood the various segments for creating the duplicate tool.
Let me go ahead and say one awesome.
So we have now saved a duplicate tool activate it for effect.
We have activated it to Haswell.
So what.
Let me do this.
Let me go ahead and test this functionality.
So go to the instructor object choose any record so other criteria is a last name and position.
Tried to kill in this record.
It is exactly the same.
Saved a record perfect so the system is telling.
Basically this is the custom message that we created and it's interesting that it does exactly the same
as the system generated message so but the first line to the system generated message in the second
lines of a custom message.
So you know you can be basically it's a custom write so you can very much modify that and as you can
see here the system is alerting me with the original record that is existing All right.
So whenever we create a record we can make use of duplicate rules and matching rules to alert the users
of the potential duplicates that may exist in the system thereby preventing creating new duplicates
in the system.
So in this scenario I make click Cancel to cancel creating the new instructor record are I may choose
this record which is the old record and I may update details in that.
In fact it is totally up to the user to decide what he or she wants to do.
They may be unaware of the existing record so that is why they are trying to create another record.
So in that scenario they may just hit cancel all if they are just trying to update some details on that
not aware that the record already exists in the system so they may go back to the original record and
just update the new fields.
All right.
One.
Hello go to the scenario.
This.
So this is how a on configure matching rules and duplicate rules and sales force and how we can implement
this a duplicate.
Management basically to control duplicates in the system by using the combination of this matching rules
and duplicate rules.