The table below lists the profile options that are used for party merge setup.
Party Merge Setup Category
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Default Data Librarian | No Default | View Only | Update | Update | Update | Update |
| HZ: Merge Master Party Defaulting | Party with Most Accounts | View Only | Update | No Access | No Access | No Access |
| HZ: Show Address Mapping Suggestions | No Default | Update | Update | Update | Update | Update |
| HZ: Show Relationship Mapping Suggestions | No Default | Update | Update | Update | Update | Update |
| HZ: Use DQM Suggested Groupings for Automerge | No | Update | Update | Update | Update | Update |
Optional. Specify a default user with the Data Librarian responsibility to assign to party and account merge requests. This default user is only used when creating a new Party Merge request or Account Merge request and the Assignee parameter is not specified.
Specify the method to use to select a party as the default merge master for new merge requests that contain multiple parties. For Automerge, the default master is automatically the party that remains after merge.
If multiple parties fulfill the condition for the methods given below, :then the party with the latest update date is selected. For example, the profile option is set to Party with Highest Certification. If five parties in the merge request have the highest certification, then the party among the five with the latest update date is the master. The methods are as follows
Party with Earliest Creation Date
Party with Highest Certification
Party with Latest Creation Date
Party with Latest Update Date
Manual
Party with Most Accounts
Party with Most Addresses
Party with Most Relationships
User Hook
The certification validation is based on the highest seeded certification level. If you want to change the highest seeded level, then update the lookup meaning of the level and update or create lower levels. See: Administering Certification.
Attention: If you select the User Hook method to use a custom defaulting process, then you must have the user hook defined. See: Creating Custom Merge Master Party Defaulting Method.
Specify if you want to show suggested address mapping on UI when a merge request is created.
Specify if you want to show suggested relationship mapping on UI when a merge request is created.
Specify if Automerge uses DQM suggested groupings to merge duplicate addresses and relationships. The match rules assigned to the following profile options determine which relationships or addresses to merge together:
HZ: Match Rule for Relationship Mapping Suggestions
HZ: Match Rule for Address Mapping Suggestions
If you want to automatically merge either relationships or addresses, but not both, you can leave the corresponding match rule profile option blank. Addresses or relationships would then be transferred from duplicate candidates to the merge master party, not merged.
If you set the HZ: Use DQM Suggested Groupings for Automerge profile option to No, then addresses and relationships are just transferred from duplicate candidates to the master.