Reference: Merge Rules for ID Data Fields
This table illustrates how Workday merges specific fields in the absence or presence of source
and target values using particular operations.
Field | Source Value | Target Value | Operation | Behavior |
|---|---|---|---|---|
Passport ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values, keep the value on the target. |
Passport ID | Yes | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when the source and target values aren't
functionally equivalent, find the most recent update and keep it on the
target. Copy and append any unique Passport data from the source to the
target. |
Passport ID | Yes | No | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source has
a value and the target doesn't, keep the source value on the target.
|
Passport ID | No | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source
doesn't have a value and the target does, keep the target
value. |
Visa ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values, keep the value on the target. |
Visa ID | Yes | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent, find the most
recent update and keep it on the target. Copy and append any unique Visa
data from the source to the target. |
Visa ID | Yes | No | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source has
a value and the target doesn't, keep the source value on the target.
|
Visa ID | No | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source
doesn't have a value and the target does, keep the target
value. |
License ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values, keep the value on the target. |
License ID | Yes | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent, find the most
recent update and keep it on the target. Copy and append any unique
License data from the source to the target. |
License ID | Yes | No | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source has
a value and the target doesn't, keep the source value on the target.
|
License ID | No | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source
doesn't have a value and the target does, keep the target
value. |
Custom ID / Other ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values, keep the value on the target. |
Custom ID / Other ID | Yes | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent, find the most
recent update and keep it on the target. Copy and append any unique
Custom ID / Other ID data from the source to the target. |
Custom ID / Other ID | Yes | No | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source has
a value and the target doesn't, keep the source value on the target.
|
Custom ID / Other ID | No | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source
doesn't have a value and the target does, keep the target
value. |
National ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values for national ID type and national ID value, keep the value on the
target. |
National ID | Yes | Yes | Custom Processing | For all person types, when the source and target don't have
matching values for national ID type and national ID value, don't merge
the records. |
National ID | Yes | No | Custom Processing | For all person types, when the source and target don't have
matching values for national ID type and national ID value, don't merge
the records. |
National ID | No | Yes | Custom Processing | For all person types, when the source and target don't have
matching values for national ID type and national ID value, don't merge
the records. |
Government ID | Yes | Yes | Custom Processing | For all person types, when the source and target have matching
values, keep the value on the target. |
Government ID | Yes | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent, find the most
recent update and keep it on the target. Copy and append any unique
Government ID data from the source to the target. |
Government ID | Yes | No | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source has
a value and the target doesn't, keep the source value on the target.
|
Government ID | No | Yes | Custom Processing | When the target is an employee or contingent worker and the source
and target don't have matching values, don't merge the records. For
other person types, when not functionally equivalent and the source
doesn't have a value and the target does, keep the target
value. |
Universal ID | Yes | Yes | Use source if target is empty. | Keep the target value. |
Universal ID | Yes | No | Use source if target is empty. | When the target has a value, keep it. When the target doesn't have
a value, set it to the value on the source. |
Universal ID | No | Yes | Use source if target is empty. | When the target has a value, keep it. When the target doesn't have
a value, set it to the value on the source. |
Universal ID | No | No | Not applicable. | Not applicable. |