Object Settings

Last published at: March 19th, 2026
Delete

On an Object's Settings page, you can enable and configure PD features for that specific object.

Next to the General Settings‍, that apply to all of Plauti Deduplicate, there are a number of settings that can be configured per Object.

Prerequisites

  • Users who are not a Salesforce Administrator can view the general settings and object settings in Deduplicate Setup, but not edit them. For non-Admin users to be able to edit the settings, they need the "Customize Application" SF system permission.

Accessing an Object's Settings

To access the object-specific settings of an Object:

  1. In Plauti Deduplicate, click the Deduplicate Setup tab.
  2. In the left-hand menu, click Object Configuration.
    The Object Configuration page opens.
  3. Click Configure  at the Object you want to configure
  4. Go to subtab Settings.
  5. Click Edit  at a setting section to edit its settings.

General

Search Index When enabled you can create a Search Index‍, used for improved duplicate search results. 
Exclude accounts that are connected via Account Hierarchy as potential duplicates
 When enabled, Accounts that are connected with each other via Account Hierarchy will not be shown as potential duplicates. Read more in Account Hierarchy and Matching‍.
The Search Index setting above needs to be enabled as well for this.
Cross Object Cross Object‍ lets you find duplicates between different objects.
Unique Import / API Bulk Insert The Unique Import‍ feature matches your imported data with your existing data. You can then merge any duplicate records that were detected.
 API Single Insert With API Single Insert‍, Plauti Deduplicate can match a single record import with your existing data. You can then merge any duplicate records that were detected.
This applies to both newly inserted and updated single records.
Chunk Size When running a Deduplicate Job, the job is divided into chunks to make the process more stable. Do not change this setting, unless you are instructed to do so by our Plauti Support team.

Security

Enforce Sharing Rules and Field Level Security When toggled to Inactive, Plauti Deduplicate will bypass the sharing rules and field level security. 
Override CRUD when performing a merge When toggled to Active, all users can merge when they have Read access to the record. 

Override sharing rules when merging records. The user needs at least Read access to be able to merge records.

 When toggled to Active, users can merge records even if they do not have the proper edit/transfer rules applied. They do need to have Read access.
Disable Set for Merge When toggled to Active, the Set for Merge‍ feature is disabled for users without delete permissions for the Object. Users with delete permissions will still be able to merge.
Delete

Find out how to solve insufficient access rights when merging records in Insufficient Access Rights when Merging Records.

Index

This section appears when you have 'Search Index' enabled above in the 'General' section.

Index creation for single records

Determines when the Index creation for single records will start. Choose from the following options:

"Deduplicate Determines the best option" - Plauti Deduplicate decides when the index is updated.
"Directly. Index is Directly available" - The index is updated right away.
"In the background. There is a delay in Index creation" - Index is updated in an apex job, started whenever Salesforce allows it to start.
Number of records returned in index search This setting determines how many records Plauti Deduplicate returns in the first step of the search procedure. Do not change this, unless you get instructions from our support team.
Chunk size in Index Creation job This setting determines the chunk size of the index creation job. Do not change this, unless you get instructions from our support team.
Index Location The location where the Search Index will be stored. Choose between the Object itself or the dedicated Index Object.
Delete

Read more about the Search Index, its storage locations and more in the Search Index knowledge article.

Merge

REGULAR OBJECT

Clone Feed Items upon Merge When enabled, the "Chatter" feed is cloned when merging records that have feed items. Cloned feed items will get the time stamp of the merge, and the user that performed the merge as poster.
When disabled, feed items from the losing records are lost upon merge.
Ignore these fields when merging Select fields that will not be visible on the manual merge page. Instead, merge rules will be applied to these fields.

CUSTOM OBJECT

In addition to the Merge settings for regular objects described above, custom objects have a few extra Merge settings.

Unique merge these related objects Select a lookup field of the related object. Upon merging two records, if their related records have the same value in the selected lookup field, then only the related record of the master record is kept.
Do not merge these related objects Select related objects that will not be merged along with their parent records. The related record of the loser record will be orphaned.

Convert

Convert settings are only available for the Lead object.

Lead Status upon Quick Convert Set the Lead Status that will be assigned to Lead records when converting them via Quick Convert‍.
Owner upon Quick Convert for new records Set the Owner that will be assigned to any new records that are created when converting Leads via Quick Convert‍.

Object Filter

When you set an Object Filter, only records that meet the filter criteria can be matched as duplicate. 

For example, set an object filter on the 'country' field, with type is 'equal'. Now, only records that have the same country value will be considered potential duplicate records. Records that are identical except for their country will not show up as duplicates.

The Object Filter only works if the Search Index is enabled and up to date for the object. See above, or read more here‍. Furthermore, the filter can be applied only to duplicate searches within an object. It does not work for Cross Object searches.

Type

None

 No filter applied; all records can be matched as potential duplicate records.

Not Equal Only records where the values of the selected field are not equal to each other are considered potential duplicate records.

Equal Only records where the values of the selected field are equal to each other are considered potential duplicate records.

Value Equal Only records where the values of the selected field are equal to the selected value are considered potential duplicate records.

Value Not Equal Only records where the values of the selected field are not equal to the selected value are considered potential duplicate records.
Field Select a field. 
Value Select a value. Only available for types 'Value Equal' and 'Value Not Equal'.

Delete Object Configuration

Delete Configuration This option deletes the Object from Plauti Deduplicate, including its entire configuration such as scenarios, result fields, merge rules et cetera. After deleting you cannot use Plauti Deduplicate anymore for this Object, until you re-add it. Upon adding the Object again, the previous configuration is lost.