Use ordinary record saves for the survivor

Context

A merged record must satisfy the same validations as an ordinary edit.

Decision

After merge-specific reference moves, Entities persistence deletes absorbed records and saves the survivor’s planned fields and collections, submitting only custom values that change.

Alternatives Considered

Write the final survivor directly. This would bypass the owner’s validation and history behavior.

Resubmit every custom value. An unchanged empty value newly marked required could prevent an otherwise valid merge.

Consequences

Ordinary save validation can fail the merge as an invalid survivor. Employee moves avoid modification stamps that would fabricate employer-history changes.