Next to the General Settings‍, that apply to all of Plauti Deduplicate, there are a number of settings and features 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 Object Configuration

To access the Object Configuration settings:

1. In Plauti Deduplicate, click the Deduplicate Setup tab.
2. In the left-hand menu, click Object Configuration.
3. The Object Configuration page opens.
   • Click Configure  at the Object you want to configure, or
   • Click + Add Object  to add a new Object to use with Plauti Deduplicate.

The Object Configuration page also displays information for each Object, such as the number of configured scenarios and scheduled jobs.
The Prevention column indicates whether duplicate prevention via Direct Processing‍ has been configured.

After clicking Configure, the Object's configuration page opens with several subtabs.

Scenarios

Scenarios decide how to compare records, how to define what a duplicate record is exactly, and where scenarios should be used. Plauti Deduplicate will return results based on the configured scenarios.

• Click + Add New Scenario  to create a new scenario.
• Click Edit  at an existing scenario to edit it.

Read more about Scenarios and how they work in Scenarios.

Object Settings

Object Settings let you define how Plauti Deduplicate behaves for this Object. Find object-specific settings related to Cross Object, the Search Index, Merging and more here.

Record Types

Objects that use record types have an additional tab 'Record Types' available in their object configuration. Here you can determine which scenarios can be used for each record type when detecting duplicate records. Furthermore, you can choose to match records of a certain record type with one, more or all record types you have in use.

Read more about the use of record types in Record Types.

Result Fields

The fields defined at the Result Fields tab of Object Settings are the record fields that are shown whenever Plauti Deduplicate return results. These are also the fields that are included in the results of a Deduplicate Job on the Deduplicate Job Results page, and in the Deduplicate Job Export‍. Furthermore, when merging duplicates manually, you can choose to display "Result Fields Only", where only the configured result fields are show for assessment when merging.

1. On tab 'Result Fields', click Configure  .
2. Select record fields from the Available Fields column and move them to the Result Fields column.

The record fields in the Result Fields column are the fields that will be displayed as Result Fields.

Read more about Result Fields in Result Fields‍.

Merge Rules

When merging records, Plauti Deduplicate calls upon the Merge Rules to pick a master record, and to determine which field values should be stored in that master record. The Merge Rules determine which master record and fields are pre-selected on the manual merge page, which fields can use AI Merge Recommendation‍, and which rules are used when executing an automated merge. 

For those cases where a merge rule might have two or more records as a result, a fallback rule can be set to determine the final result.

Read more in Merge Rules‍.

Direct

Deduplicate Direct, also known as Direct Processing, merges and converts duplicate records at entry point without any user interaction. It processes records coming from Web-to-Lead, Unique Import / API Bulk Insert, Deduplicate Apex Api, Flow actions, or API Single Insert / Update records.

• Click Configure  to edit the Direct Processing settings for merging and converting.

Read more in Direct Processing.

Cross Object

With Cross Object you can search for duplicate records across different Objects. Cross Object is configured per object pair.

1. Enable Cross Object on the object's Settings tab.
2. Configure Cross Object on the object's Cross Object tab.
3. Click Add Cross Object  to add an object pair.
4. Click Configure Cross Object  to configure an object pair.
5. In the Configure Cross Object modal, add Cross Fields. This determines which fields should be compared between the objects. Only those fields that are defined in your Scenarios can be mapped.

Read more in Cross Object.

Index Batch

Search Indexes are created on the Index Batch tab. When creating a Search Index, a special key will be generated for your records, which lets Plauti Deduplicate compare them in a more advanced way. For example, using the Fuzzy Matching Methods‍ in a scenario with the Search Index enabled and generated will yield better results when matching records that are not 100% equal, with a spelling error or different format.

1. Enable Search Index on the object's Settings tab.
2. Generate a Search Index on the object's Index Batch tab.
3. Click Action  to select one of the options for generating a Search Index.
4. Generate a full or incremental Search Index job to run within Salesforce, on Plauti Desktop or Server, or on Plauti Cloud.
5. If selected to run on Plauti Desktop/Server/Cloud, open that app and start the "Search Index" job.

Read more about the Search Index and its configuration options in Search Index‍.

Predefined Filters

Use a Predefined Filter to search within a subset of data. Predefined Filters can be used at a number of places, such as in a Deduplicate Job filter, the Overall Job Results, the Embedded Overall Job Results, or in a search in Apex API, Rest API, or the Direct Processing API. 

Using Predefined Filters for custom objects requires some additional configuration‍.

1. Click Add Filter  to create a Predefined Filter.
2. Click Configure  to edit a Predefined Filter.
3. Add a new Filter Rule by clicking the "+"  icon.
4. Select the field, expression and value to filter on.
5. Add Filter Logic if you added two or more Filter Rules.

Read more in Predefined Filters‍.