Merging Companies and Persons

Two company or person records can be merged into a single record in Aurea CRM.Web to remove duplicates.

The merge process (MergeRecords,see Processes) is called using the menu actions A_WebMerge_Companies and A_WebMerge_Persons (and D_WebMerge_Multiple_Companies und D_WebMerge_Multiple_Persons for multi-select).

The process can be started from a single source record (the user then selects the target record in the 1st step) or with both records in that case, the user starts with the conflict resolution step. If more than two records are selected, the menu action is disabled.

The MergeRecords process supports the following parameters which you can specify as input arguments for the menu action:

• fixedFilterName: "<InfoAreaId>.<FilterName>" adds a fixed filter for the search.
• copyFields: <field names or numbers> defines the fields to copy from the source record into the search.
• mergeOptions: ["userDecides", "sourceWins", "targetWins", "mostRecentWins"] array defining which conflict resolution options are displayed beneath the merge overview under Merge method.
• defaultMergeOption sets the default merge option.
• showEqualValues: <true|false> defines whether fields with identical content should be displayed in the merge overview in case of a conflict. (It some case it may be helpful to display fields with identical content, because e.g. the correct postal code is hard to judge if you do not see the corresponding city; on the other hand that means that users sees a lot of fields, including system fields and fields which they probably haven’t seen before.)
• useTransaction: <true|false> If true (default), the merge is executed using transactions. For further details, see Support for Database Transactions.
• listParams: <Name>,<Value>;<Name>,<Value>;... defines listParams for the search results list. For further details, see ListParams.

The merge overview (of source and target record) uses the Field Group FIMergeOverview / KPMergeOverview / PEMergeOverview / CPMergeOverview. (The Details controls in these Field Groups only support one column.)

The actual merge process may take some time depending on the amount of child records.

The merge is performed with the rights of the currently logged-in user. Therefore conflicts may occur during the merge process which the user cannot solve due to his rights definition (e.g. because he cannot access this data). Since merging records where the user cannot see the contents makes little sense and can lead to inconsistencies, the merge process is stopped in this case. The merge then has to be performed by a person with adequate rights (e.g. an administrator).