Reference: Merge Rules for Personal 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:
We merge personal information and contact information, with the exception of that data on recruiting job applications.
- 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.
Field | Source Value? | Target Value? | Operation | Behavior |
|---|---|---|---|---|
Sexual Orientation and Gender Identity | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Sexual Orientation and Gender Identity | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, keep the most recent update on the target, based on the effective date, if the source and target have unique values for:
When the effective dates are the same on both the source and target, we use the completed date. |
Sexual Orientation and Gender Identity | Yes | No | Last Updated (from Audit) | When not functional equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Sexual Orientation and Gender Identity | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Citizenship Status | Yes | Yes | Append | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Citizenship Status | Yes | Yes | Append | When not functionally equivalent, keep the most recent update on the target, based on the effective date, if the source and target have unique values for:
When the effective dates are the same on both the source and target, we use the completed date. |
Citizenship Status | Yes | No | Append | When not functional equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Citizenship Status | No | Yes | Append | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Date of Birth | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Date of Birth | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, keep the most recent update on the target, based on the effective date, if the source and target have unique values for:
When the effective dates are the same for both the source and target, we use the completed date. |
Date of Birth | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Date of Birth | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Date of Death | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Date of Death | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, keep the most recent update on the target, based on the effective date, if the source and target have unique values for:
When the effective dates are the same on both the source and target, we use the completed date. |
Date of Death | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Date of Death | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Gender | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Gender | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, find the most recent update based on the effective date and keep it on the target. When the effective dates are the same on both the source and target, we use the completed date. |
Gender | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Gender | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Gender Identity (New) | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values for:
|
Gender Identity (New) | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, keep the most recent update on the target, based on the effective date, if the source and target have unique values for:
When the effective dates are the same on both the source and target, we use the completed date. |
Gender Identity (New) | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Gender Identity (New) | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Sexual Orientation (New) | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values. |
Sexual Orientation (New) | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, find the most recent update based on the effective date and keep it on the target. When the effective dates are the same for both the source and target, we use the completed date. |
Sexual Orientation (New) | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Sexual Orientation (New) | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |
Pronoun (New) | Yes | Yes | Last Updated (from Audit) | When functionally equivalent, keep the value on the target if the source and target have matching values. |
Pronoun (New) | Yes | Yes | Last Updated (from Audit) | When not functionally equivalent, find the most recent update based on the effective date and keep it on the target. When the effective dates are the same on both the source and target, we use the completed date. |
Pronoun (New) | Yes | No | Last Updated (from Audit) | When not functionally equivalent and the source has a value and the target doesn't, keep the source value on the target. |
Pronoun (New) | No | Yes | Last Updated (from Audit) | When not functionally equivalent and the source doesn't have a value and the target does, keep the target value. |