Merge outcomes

AD
DM
DS

The following sections detail merge outcomes by ownership at the record and field level.

Merges by data stewards

The following table illustrates outcomes for merges initiated by data stewards.

The columns indicate the ownership (orange - Veeva-owned, gray - customer owned) for both the winning and losing record.

The rows indicate the ownership of all fields and records associated with the merge, along with the merge outcome for each.

Fields / Keys
Winner
Loser
Winner
Loser
Winner
Loser
HCP/HCO fields  Orange values persist -
HCP/HCO fields Winner values persist unless empty1  Winner values persist
Address record Match losers and winners and merge duplicates2 Match losers and winners, merge duplicates
Parent HCO record Match losers and winners and merge duplicates2 Match losers and winners, merge duplicates
License record Match losers and winners and merge duplicates2 Match losers and winners, merge duplicates
Custom key Retain winning keys and copy losing keys to winner
Address fields -3 Orange values persist -
Address fields Winner values persist unless empty1 Winner value persists
Parent HCO fields -3 Orange values persist -
Parent HCO fields Winner values persist unless empty1 Winner value persists
License fields -3 Orange values persist -
License fields Winner values persist unless empty1 Winner value persists
Notes

1 Values explicitly set to NULL will persist; empty or blank values will not.

2 Can prevent gray records by setting the advanced source subscription property job.merge.allowCustomerOwnedChildren = "false"

3 Not applicable: Managed by Veeva OpenData

Automatic merges

The following table illustrates outcomes for automatic merges.

The columns indicate the ownership (orange - Veeva-owned, gray - customer owned) for both the winning and losing record.

The rows indicate the ownership of all fields and records associated with the merge, along with the merge outcome for each.

Fields / Keys
Winner
Loser
Winner
Loser
Winner
Loser
HCP/HCO fields -1  Orange values persist -
HCP/HCO fields Value from more trusted source retained2
Address record -1 Match losers and winners and merge duplicates3 Match losers and winners, merge duplicates
Parent HCO record -1 Match losers and winners and merge duplicates3 Match losers and winners, merge duplicates
License record -1 Match losers and winners and merge duplicates3 Match losers and winners, merge duplicates
Custom key Retain winning keys and copy losing keys to winner
Address fields -1 Orange values persist -
Address fields Value from more trusted source retained2
Parent HCO fields -1 Orange values persist -
Parent HCO fields Value from more trusted source retained2
License fields -1 Orange values persist -
License fields Value from more trusted source retained2
Notes

1 Not applicable: Managed by Veeva OpenData

2 If values are from the same source, retain newer value

3 Can prevent gray records by setting the advanced source subscription property job.merge.allowCustomerOwnedChildren = "false"

Veeva OpenData records

The following table illustrates outcomes based on merge actions affecting Veeva-owned (orange) records. In the Veeva OpenData master instance, Record A is merged into Record B.

Customer instance prior to merge User action (manually or through DCR) Outcome

Losing Record A exists

User updates Record A
  • Record A is updated.
  • Winning Record B is automatically downloaded.
  • When viewing profile page for Record A, Record B is presented. Attempts to display Record A (for example, by altering the URL), result in Record B being displayed.

Winning Record B exists

User updates Record B
  • Winning Record B is updated.
  • Record A is not downloaded to the customer's Network instance.

Losing Record A exists

Winning Record B exists

User updates Record A
  • Record A is updated.
  • Winning Record B is also updated (if required).
  • When viewing profile page for Record A, Record B is presented. Attempts to display Record A (for example, by altering the URL), result in Record B being displayed.

Losing Record A exists

Winning Record B exists

User updates Record B
  • Winning Record B is updated.
  • Record A is also updated and becomes a merge loser.
  • Attempts to display Record A (for example, by altering the URL), result in Record B being displayed.