Unique Checkbox primary address examples

AD
DM

Use these examples to understand how Network calculates primary for address updates.

Note: These examples do not include any custom logic that you can specify in the Unique Checkbox field configuration.

Network will calculate the primary for addresses that are added or updated depending on the options that you have selected for a Unique Checkbox primary address field. Any combination of the options can be selected.

Review the sections below to understand how primary is calculated when addresses are added or updated using the following actions:

  • source subscriptions
  • updates on the profile page
  • updates in data change requests
  • change request API

Each example includes a number (for example, A1, D2, and so on) in the Workflow Example column to refer to a diagram. You can refer to the diagram in the Workflows section below to see how Network decides whether a primary should be calculated based on the address and the options that are enabled for the primary field.

Understanding how Network calculates primary for OpenData updates

Network's primary calculation when addresses are downloaded from or synced with Veeva OpenData depend on the options that you have selected for a primary address field. Any combination of options can be selected.

Review the sections below to understand how primary is calculated when addresses are added or updated using the following actions:

  • Downloading records from Veeva OpenData (using OpenData subscriptions or the Ad Hoc Download or Download from OpenData buttons).
  • Syncing a record with Veeva OpenData (using the Sync with OpenData button).

Understanding how Network calculates primary for merge and unmerge

Merge

A primary is calculated by Network if neither the merge winner nor the loser contributed a primary and the The record DOES NOT HAVE a primary address option is enabled.

If the winning record contributes a primary address, the winner's address remains primary after the merge. However, if the winner's primary is inactive/invalid and the loser contributed a primary, the loser's address becomes primary after the merge. ]If the loser's address is inactive/invalid, Network will calculate a primary from all the active and valid addresses on the merged entity.

If the winner did not contribute a primary and the loser contributed a primary, the loser's address will remain primary after the merge. However, if the loser's address is inactive/invalid, Network will calculate a primary from all the active and valid addresses on the merged entity.

Unmerge

When records are unmerged from each other, any fields that were set as primary on the original records are recovered.

A primary is calculated in the following situations:

  • None of the source views contributed a primary and the following option is on: The record DOES NOT HAVE a primary address.
  • An inactive address is primary in the source views and the following option is on: The status of the primary address is INACTIVE.
  • An invalid address is primary in the source views and the following option is on: The status of the primary address is INVALID or DELETED.

Workflows

These workflows illustrate how Network determines if a primary should be calculated based on the addresses and the options that you have selected for the primary field. The letters in the purple circles; for example, , correspond to the examples in the tables above, so you can follow the decision points.

Tip: Right-click on the image to open it in a new browser tab so you can zoom in on the details.