Duplicate Check Settings

Scene: Leads, accounts, and contacts are the main data information carriers of CRM. The unique identification in different industries is often multi-dimensional. To eliminate the repetitive information that occurs in human operations, it needs the support of customized complex rules.

1. New Duplicate Check

It is mainly used to check the duplication according to this rule when the specified object is manually created.

  • Enable New Duplicate Check: If it is enabled, the records (including obsolete data) under the object can be matched according to the duplicate check rules when creating a new object record. If a duplicate record is matched, the user will be prompted that there is a duplicate record. Of course, you can ignore it and continue to create a new object record.
  • Support New Duplicate Check: accounts, contacts and leads.
  • Duplicate Check Logic Settings: Match according to the system preset field of the object. Exact or fuzzy queries of combinable fields. If an account's "Account Name" is partially repeated and "Telephone" is completely repeated, it is determined to be a duplicate account.
  • Duplicate Check Result Display: If duplicate records are matched, the displayed fields can be configured. Because duplicate records may not have data authority for the duplicate check personnel, the fields visible after the duplicate check can be configured to ensure data security and prevent the duplicate check personnel from stealing customer information based on the duplicate check results.
  • Duplicate Check Rule-Field Disabling Logic:
    • Fields that have been disabled/deleted do not participate in duplicate checking:
    • Fields used in duplicate checking rules are not allowed to be disabled in field management.
  • Supported field types for duplicate checking: single choice, multi-line text, mobile phone, sign-in component, single-line text, URL, country, province, city, district, person in charge, creator, external person in charge, location type field

2. Duplicate Check Tool

It is mainly used for duplicate check logic configuration when checking duplication through the "duplicate check tool".

  • Enable Duplicate Check Tool: If at least one of the three objects that support plagiarism check is enabled, the "Duplicate Check Tool" will be visible in "My Workbench-Home" and support record query.
  • Support New Duplicate Check Objects: accounts, contacts and leads.
  • Duplicate Check Logic Settings: Match according to the system preset field of the object. Exact or fuzzy queries of combinable fields. If an account's "Account Name" is partially repeated and "Telephone" is completely repeated, it is determined to be a duplicate account.
  • Duplicate Check Result Display: If duplicate records are matched, the displayed fields can be configured. Because duplicate records may not have data authority for the duplicate check personnel, the fields visible after the duplicate check can be configured to ensure data security and prevent the duplicate check personnel from stealing account information based on the duplicate check results.

3. Import Duplicate Check

  • Scene: Duplicate check is required when order is imported.
  • Accounts, contacts, leads objects: will not verify joint duplicate check rules;
  • If fuzzy matching is configured for duplicate check rule conditions, duplicate check verification will not be performed during import, and data import will not be blocked;
  • When the object is configured with a uniqueness rule, both rules will go away.
  • Notes: When the duplicate check logic is set to And, the imported data contains null values, and the result display is not repeated. For example, if A&B&C is set, if there is a null value among A, B, and C, it will be displayed as non-duplicate and can be imported success

4. Opportunity Duplicate check

In order to prevent multiple sales in the enterprise from following up on the same account and the same project, you can enable "Forbid creating duplicate opportunity names under the same account".

5. Simple Duplicate Check

  • Configure and (AND) Relationship: under the account object, we set duplicate check rules for the "account name", "account short name", "address" and "mobile number" fields

  • Configuration or (OR) Relationship: Under the account object, we set duplicate check rules for the "account name", "account short name", "address" and "mobile number" fields

  • Configure and (AND) & or (OR) Relationship: Under the account object, we set the duplicate check rules for the fields of "account name", "account short name", "address" and "mobile number". There are the following three pieces of data:

2023-02-27
0 0