Merging Large Numbers of Records
NetSuite can merge an unlimited number of records using the Mass Update functionality. Administrators set the rules for the merge process to determine which record in a set of duplicates is the primary record and configure the criteria to control the search results.
System notes are not transferred from duplicate entity records to the primary entity record during a merge. Merging entities updates the system notes and last modified date for all transactions associated with the duplicate entity or entities. The system notes for these transactions will indicate that they were updated by the Duplicate Resolution process.
Merging entities is a data-intensive operation, and complex merges of many records such as transactions, custom fields, or workflows may time out when processing. You should test the merge process in a sandbox account first to ensure that it can be completed.
You should designate the entity with the most transactions as the primary record and entities with fewer transactions as duplicates to reduce the time it takes to complete the merge. You should also avoid merging entities with large numbers of transactions whenever possible.
You must have full permissions for the entity types you are merging. For example:
-
You must have full permissions for Vendors to merge two vendors.
-
You must have full permissions for both Contacts and Customers to merge Individual Customers, which are composed of both.
-
You must have full permissions for both Customers and Vendors to merge into a Customer/Vendor entity.
To merge large numbers of duplicate records:
-
Go to Lists > Mass Update > Mass Updates.
-
In the Action column, expand the Duplicate Resolution options, and click the type of record you want to merge.
-
Use the dropdown list in the Master Selection Mode field to define the primary record. You can use the following modes:
-
Created earliest – This mode selects the record that was created first as the primary record.
-
Most populated fields – This mode selects the record that has the most fields containing data as the primary record.
-
Most recent activity – This mode selects the record with the most recent activity as the primary record.
-
-
Use the Record Selection Mode list to define which records are selected. You can use the following modes:
-
All from duplicate group – Both the primary record and the duplicate records are selected from the complete group of duplicate records, and search results are used only to determine the groups.
-
Master from duplicate group – The primary record is selected from the whole group, and duplicates are selected from the search results only.
-
Master and duplicates from search only – Both the primary record and the duplicate records are selected only from the search results.
-
You can use various criteria to define which records are included in the operation and schedule regular duplicate merge operations to take place automatically at regular intervals.
Merge Time Out Error
A merge time out error occurs when the system fails to merge due to the amount of information which needs to be remapped. You can find the error log at: Relationships > Mass update > Duplicate Resolution Status.
If this error occurs, an administrator in your company or a role with the Merge Prolong Timeout permission can extend the time before a timeout occurs and reattempt the merge. These roles can check the Prolong Timeout box on the Merge page for the record type they are merging.
To set this role, Go to Setup > Users/Roles > Manage Roles. Click edit next to a role to add the permission to, and on the Permissions subtab, add the Merge Prolong Timeout role with full permissions to the Lists subtab.