When using Duplicate Prevention in the standard Lightning Entry page, Plauti Deduplicate is limited to showing only a text message. To show the actual duplicate records while you are working on a record, replace the native entry page with the Deduplicate Entry Lightning Component. This way you can also display a warning or even prevent users from creating or updating a record if duplicates were found.

the Deduplicate Entry page

How it works

The Deduplicate Entry page will show up after clicking the button to create a new record or edit an existing record. Deduplicate Entry will check for duplicates in real-time, so potential duplicates will start appearing while users are filling out the fields.

For each duplicate record found, it will show the Score, the Result Fields as configured in the settings for that particular Object, and a button to view the potential duplicate record in a new tab. 

Based on the duplicates found users can then decide to update an existing record, or create or update the current record after all. Optionally, you can prevent users from creating or updating a record if duplicates were found.

For now, Deduplicate Entry is not available for the Task object.

To configure Deduplicate Entry:

1. First replace the entry page
2. Then apply scenarios
3. Optionally, add full or partial insert blocking

1. Replacing the entry page

First, replace the Salesforce native entry page with the Deduplicate Entry page:

1. Go to Salesforce Setup> Object Manager.
2. Open the Object where you want to use the Deduplicate Entry page. 
3. At left, go to Buttons, Links, and Actions.
4. At the 'New' line, click Edit.
5. At 'Lightning Experience Override', click Lightning Component, and select the dupcheck:dc3EntryRecordForm Lightning Component.
6. Click Save.
7. Repeat steps 5. and 6. for the Edit button: still in 'Buttons, Links and Actions', edit the 'Edit' line. 

2. Applying a scenario

Then apply at least one scenario to manually inserting or updating a record.

To find duplicate records when creating or updating a record with the Deduplicate Entry override page, one or more scenarios should be enabled for this.

1. Go to Deduplicate Setup > Object Configuration.
2. At the Object(s) where you want to use Deduplicate Entry, click Configure.
3. At the Scenario tab, find and edit the scenario you want to use for Deduplicate Entry or create a new one.
4. In the Scenario configuration, at Apply to, 
   • Add 'Manual Insert Prevention' to use Deduplicate Entry when creating a new record, and
   • Add 'Manual Update Prevention' to use Deduplicate Entry when updating an existing record.
5. Click Save.

Blocking entry (optional)

Optionally, you can prevent users from saving a record when duplicates have been found. Either block saving completely, or initially block but offer an 'Ignore and Save' option.

Fully blocking a duplicate entry

To ensure records cannot be saved if duplicate records were found:

1. Go to Deduplicate Setup > Settings.
2. At 'Duplicate Prevention in Native Entry Page Lightning', make sure the toggle switch is set to Enabled.

Now, when a duplicate was found when creating or editing a record, the record cannot be saved.

Blocking a duplicate entry with an option to override

To enable record blocking, but leave an option to override for certain users:

1. Go to Deduplicate Setup > Settings.
2. At 'Duplicate Prevention in Native Entry Page Lightning', make sure the toggle switch is set to Enabled.
3. Go to Salesforce Setup > Permission Sets or Profiles.
4. Open the permission set or profile that should be able to ignore the block.
5. Go to its Object Settings and open the Object(s) where you want to use Duplicate Prevention.
6. In the Field Permissions section, find the Disable Deduplicate field. 
7. Make sure the permission set or profile has at least Read access to the Disable Deduplicate field.

Now, when a duplicate was found when creating or editing a record, the record cannot be saved, except when the user has a permission set or profile that has Read access to the Disable Duplicate Check field: then they can save the record even if a duplicate record is present. A warning is shown informing them that duplicates were found, but they can click Ignore & Save to save the record anyway.

Blocking entry with the native SF form

Even if you choose not to use the Plauti Deduplicate Entry override form, you can still use Plauti Deduplicate to find and block duplicates when creating or updating records.

1. Apply one or more scenarios as described in step 2. Applying A Scenario above.
2. Block saving duplicate records by enabling 'Duplicate Prevention in Native Entry Page Lightning' in Deduplicate Setup > Settings.
3. Allow override when blocked by adding the Disable Deduplicate checkbox to the page layout (optional). When a duplicate record was found, and users tick the Disable Deduplicate checkbox on the record, they can still save the record via an 'Ignore & Save' button.

So with applying one or more scenarios, and the 'Duplicate Prevention in Native Entry Page Lightning' setting enabled, users will not be able to save a record if duplicates were found to exist; but if you add the Disable Deduplicate checkbox to the page layout, and they have edit rights to that checkbox, they will still be able to save it if needed.

For non-standard and custom objects, you need to create the 'Disable Deduplicate' checkbox first, and the hard-block will only work when the Apex Trigger is created. Find out how in steps 2 and 3 of this article.