Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2023-06-23
Reference: Merge Rules for Name Data Fields

Reference: Merge Rules for Name Data Fields

This table illustrates how Workday merges specific fields in the absence or presence of source and target values using particular operations. The table includes these terms:
  • Custom Processing: The Behavior column provides a description of how we process the data.
  • Functionally Equivalent: Workday considers the data values on the source and target records to match.
These merge rules apply to all person types except employee. For an active employee, you can use the
Manage Match Rules
 task to configure these Employee Merge options:
  • Append the data from the source to add any different data on the source to the target employee record.
  • Don't append data from the source to leave any different data on the source record.
We merge personal information and contact information, with the exception of that data on recruiting job applications.
Field
Source Value?
Target Value?
Operation
Behavior
Legal Name
Yes
Yes
Custom Processing
When a Legal Name is added through an event, we use that name. When a Legal Name is not added on the source or target through an event, and the source and target are functionally equivalent, keep the value on the target when the source and target have matching values.
Legal Name
Yes
Yes
Custom Processing
When a Legal Name is added through an event, we use that name. When a Legal Name is not added on the source or target through an event, and the source and target are not functionally equivalent, find the most recent update—the data most recently entered on either the source or target based on the effective date—and keep it on the target. If the effective dates are the same on both the source and target, then we use the completed date. Append any additional names as Additional Names to the target.
Legal Name
Yes
No
Custom Processing
When a Legal Name is added through an event, we use that name. When a Legal Name is not added on the source or target through an event, and the source and target are not functionally equivalent, and the source has a value and the target doesn't, keep the source value on the target.
Legal Name
No
Yes
Custom Processing
When a Legal Name is added through an event, we use that name. When a Legal Name is not added on the source or target through an event, and the source and target are not functionally equivalent, and the source doesn't have a value and the target does, keep the target value.
Preferred Name
Yes
Yes
Custom Processing
When functionally equivalent, keep the value on the target when the source and target have matching values.
Preferred Name
Yes
Yes
Custom Processing
When not functionally equivalent, find the most recent update on the source based on the completed date and move it to the target. Append any additional names as Preferred Names to the target.
Preferred Name
Yes
No
Custom Processing
When not functionally equivalent and the source has a value and the target doesn't, move the source value to the target.
Preferred Name
No
Yes
Custom Processing
When not functionally equivalent and the source doesn't have a value and the target does, keep the target value.
Additional Name
Yes
Yes
Custom Processing
When functionally equivalent, keep the value on the target when the source and target have matching values.
Additional Name
Yes
Yes
Custom Processing
When not functionally equivalent, add additional name from the source to the target.
Additional Name
Yes
No
Custom Processing
When not functionally equivalent and the source has a value and the target doesn't, append the source values on the target.
Additional Name
No
Yes
Custom Processing
When not functionally equivalent and the source doesn't have a value and the target does, append the target values.