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.
These merge rules
apply to all person types except employee. When you merge an employee record, you
have the option to append data that doesn't match from the source to the target. You
also have the option to leave that data on the source.
Field | Source Value? | Target Value? | Operation | Behavior |
|---|---|---|---|---|
Legal Name | Yes | Yes | Custom Processing | When functionally equivalent, keep the value on the target when the
source and target have matching values. |
Legal Name | Yes | Yes | Custom Processing | When not functionally equivalent, find the most recent update and keep
it on the target. Append any additional names as Additional Names to the
target. |
Legal Name | Yes | No | Custom Processing | When 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 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 and keep
it on 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, keep the source value on 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. |