X hits on this document





65 / 95

CounterPoint SQL V8.3.5 Release Notes


When you start the customer merging process, the Crystal Reports Viewer displays the MERGE CUSTOMERS report. This report lists the customer pairs you are about to merge.

If you want to maintain a printed record of customer merging activity, you must print the MERGE CUSTOMERS report at this point. You will not be able to reproduce the report later, although you can view each customer merging event in System / Views / Events.


You can also print the MERGE CUSTOMERS report by clicking the Print button on the Merge Customers window.

When you close the MERGE CUSTOMERS report, the following message appears, prompting you to confirm that you want to merge the customers you have specified.

Click Yes to begin the merging process.

A progress indicator appears, informing you of the status of the merging process.

When the merge is complete, the following message appears, listing the Event # for the corresponding Merge Customers event, as well as the number of successful and unsuccessful merge transactions.

Click OK to return to the Merge Customers window.

If all customer pairs were merged successfully, the customer merging group is automatically removed from the database. If any errors occurred, the group remains on file, allowing you to make the necessary changes and perform the merging process again.

Merging customers in a Multi-Site environment

In a Multi-Site environment, merging customer records is only allowed at the Hub site. You cannot merge customer records at Remote sites.


Merging customers at the Hub site does not update records at Remote sites. To avoid replication errors and database conflicts, you MUST replicate your data immediately before merging, merge customers at the Hub site, and then replicate again immediately after the merging process is complete.

If you do not follow this procedure and a user at a Remote site updates a record that references a merged customer number while the Hub site is merging, you WILL encounter replication problems.

Merging custom fields

If you have created custom fields—either in custom tables or in standard CounterPoint tables—that need to be merged as part of the customer merging process, you must add the corresponding table to the USP_MERGE_CUST stored procedure.

Document info
Document views321
Page views321
Page last viewedFri Jan 20 16:17:28 UTC 2017