Duplicate Record Detection and Merge Feature in NetSuite

The Duplicate Detection & Merge feature aids organizations in identifying and resolving duplicate records within their NetSuite accounts, ultimately streamlining record management and maintaining data integrity.

How to Enable Duplicate Detection

Administrators can activate the Duplicate Detection & Merge feature by navigating to Setup > Company > Enable Features on the Company subtab within the Data Management section. From there, administrators can customize the types of records to monitor for duplicates and select which fields are relevant for the detection process.

Supported Record Types

This feature can detect duplicates across four main record types:

• Customer
• Vendor
• Partner
• Contact

Note: Private contacts are excluded from the Duplicate Detection process.

Permissions Required for Merging Records

To successfully merge duplicate records, users must have full permissions for the entity types involved. For example:

• Full permissions for Vendors is necessary to merge two vendor records.
• Merging Individual Customers requires full permissions for both Contacts and Customers.
• Full permissions for both Customers and Vendors are needed to merge into a Customer/Vendor entity.

Cross-Subsidiary Duplicate Detection

Duplicate detection can span across subsidiaries. To enable this feature, make sure to activate the Detect Duplicates Across Subsidiaries option at Setup > Company > Company Management > Duplicate Detection. The primary subsidiary information for potential duplicates will be displayed in the Primary Subsidiary column.

System Notes and Merge Limitations

When merging duplicates, be aware that system notes from the duplicate records do not transfer to the primary record. However, the merging process updates the system notes and last modified date for all associated transactions, reflecting that they have been modified through the Duplicate Resolution process.

Performance Considerations

Bear in mind that merging records can be data-intensive, particularly when handling many transactions, custom fields, or workflows. It's advisable to conduct tests in a sandbox environment to verify the merges can be executed successfully.

To optimize the merging process, designate the record with the highest transaction volume as the primary entity, while designating those with fewer transactions as duplicates. Try to avoid merging entities with a large number of transactions whenever feasible.

Duplicate Notifications

With the Duplicate Detection feature enabled, users receive notifications if they attempt to save a record that may be a duplicate. Notifications occur in two main scenarios:

• When creating a new record that matches existing records based on predefined criteria, a warning appears, providing a link to potential duplicates. If users have permission to view those records, they can click through to resolve them.
• When modifying a record through Quick Add or Edit that results in a duplicate, a popup warning is issued.

Managing Duplicate Records

Users can also access Lists > Mass Update > Entity Duplicate Resolution to identify and resolve multiple duplicates at once using specified criteria. This mass update feature is particularly useful for efficiently managing large volumes of duplicate records in a single operation.

For further details on managing duplicates, see:

• Merging or Deleting Duplicate Records
• Merging Large Numbers of Records
• Merging Different Types of Records
• Words Excluded from Duplicate Detection Matching

Related Topics

• Managing Records and Transactions
• Working with Records
• Working with Groups
• Working with Transactions
• Working with Lists
• Near Match Detection

Source: This article is based on Oracle's official NetSuite documentation.

Key Takeaways

• Duplicate Detection helps maintain data integrity by identifying and merging duplicate records in NetSuite.
• Administrators can customize detection criteria for different record types.
• Users must have the necessary permissions to merge records effectively.
• Merging is a data-intensive task that should be tested in a sandbox environment first.
• Notifications alert users about potential duplicates, making record management easier.