Reference: Unmerge Rules for Name Data Fields
This table illustrates how Workday unmerges specific fields in the absence or presence of
source and target values using particular operations.
Field | Operation | Behavior |
|---|---|---|
Legal Name | Custom Processing | When an event change occurs (add, delete, update) on the person after the merge, rescind
the event before attempting to unmerge the records. |
Legal Name | Custom Processing | When a change (add, delete, or update) didn't create an event,
Workday allows the unmerge. After unmerging the records, Workday
keeps any additions on the target, puts any deletions back on the
target, and keeps any updates on the target. Workday doesn't revert
the updates. Workday also returns the source to its original
values. |
Preferred Name | Custom Processing | When an event change occurs (add, delete, update) on the person after the merge, rescind
the event before attempting to unmerge the records. |
Preferred Name | Custom Processing | When a change (add, delete, or update) didn't create an event,
Workday allows the unmerge. After unmerging the records, Workday
keeps any additions on the target, puts any deletions back on the
target, and keeps any updates on the target. Workday doesn't revert
the updates. Workday also returns the source to its original
values. |
Additional Name | Custom Processing | When an event change occurs (add, delete, update) on the person after the merge, rescind
the event before attempting to unmerge the records. |
Additional Name | Custom Processing | When a change (add, delete, or update) didn't create an event,
Workday allows the unmerge. After unmerging the records, Workday
keeps any additions on the target, puts any deletions back on the
target, and keeps any updates on the target. Workday doesn't revert
the updates. Workday also returns the source to its original
values. |