The table below lists the profile options that are used for party merge deployment.
Party Merge Deployment Category
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Automerge Master Party Selection | No Default | Update | Update | Update | Update | Update |
| HZ: Number of Workers Used by Party Merge Program | No Default | Update | Update | Update | Update | Update |
| HZ: Return User Name in GET APIs | Yes | Update | Update | Update | Update | Update |
| HZ: Submit Suggested Person Merge Request | No | Visible | Update | Update | Update | Update |
Determine how the merge master is selected during Automerge upon System Duplicate Identification.
Determine the number of parallel workers to use for the Party Merge program when invoked by Automerge to automatically merge duplicates. Workers are processes that run at the same time to complete a task that would otherwise take longer with a single process. This profile option does not apply to running the Party Merge program outside of Automerge.
Specify whether to return the user name or the user ID. Enter Yes to return the user name, and No to return the user ID.
Use this profile option to automatically submit the suggested person merge request after the related organization parties are merged.
If the profile is set to Yes, then the suggested person merge request is automatically submitted.
For example, if organization party A has a related a contact, A1 and organization party B has a related contact, B1. If organization party A and party B are merged and the corresponding contacts A1 and B1 are merged, then the suggested person parties for A1 and B1 are automatically merged.
Set this profile to No to manually submit the suggested person merge request. The default value is No, if it is not set.