Primary type custom fields


Administrators and data managers can create multiple primary custom fields in the Network data model. Creating a primary custom field enables you to designate a "best" object to support your business practices. For example, for incentive compensation, you might specify a primary address for all the health care providers in a business unit. You can report on HCPs and their primary address and export the list from Network to use for territory alignment and incentive compensation in another system.

There are two configurations available for primary type custom fields:

  • Network Calculated - Use if you want Network to calculate what the primary should be. Only one field per object can use this configuration in an instance. If a field on an object is already defined as Network Calculated, the option in the Configuration list is dimmed.

    The Network Calculated configuration is available for address and Parent HCO objects only.

  • Unique Checkbox - Use if you want the primary to be managed by users. Only one object can be defined for each primary field. An object can have multiple Unique Checkbox primary fields, for example; an HCP record can have multiple primary addresses - one for each business unit or therapeutic area.

    This configuration is available on all Network and custom sub-objects and relationship objects. For address sub-objects only, there are additional options to allow Network to recalculate primary addresses in specific situations.

    For detailed information about using this configuration for addresses, see Unique Checkbox with primary address calculations.

Comparison of primary configurations

Review the table to compare the two types of configurations for primary custom fields.

  Unique Checkbox Network Calculated
Commonalities Business logic ensures that only one record can be primary.
Differences Multiple primary fields are allowed for each object. Only one primary field is allowed for each object.
  Available on all Veeva and custom sub-object and relationship objects. Available on address and parent affiliation objects.
  Configuration options allow for more granular control over when primary address is calculated. For more information, see Unique Checkbox with primary address calculations. Always ensures there is an active and valid primary

Viewing primary designations on the profile page

On the Profile page, primary indicators display when a primary field is set for an object. The Primary badge displays and the primary tag identifies the business units (Unique Checkbox) or Global Primary (Network Calculated).

Create primary custom fields

Administrators and data managers can create primary custom fields in the Network data model. For each primary field type, administrators can decide whether primary is automatically calculated by Network or managed by users (Unique Checkbox configuration). Existing primary fields for the address or Parent HCO object can be changed so that they are user-managed.

To create a primary type field:

  1. In the Admin console, click Data Model and select the Customer Master domain.
  2. Click the Address object.
  3. In the Fields section, select a field that is already a primary type or click Add Field to create a new one.

  4. Type a Name and Description for a new field.
  5. In the Type field, select Primary.
  6. In the Configuration list, select one of the options:
    • Network Calculated - Network uses business rules to automatically calculate what the primary address or Parent HCO should be. If the address or Parent HCO is invalidated or inactivated, Network recalculates the next best primary.

      Only one field for each object can use this configuration in a Network instance. It is only available for address and Parent HCO objects.

    • Unique Checkbox - Users can manage this primary field. Only one object can be set to primary for the field. Primary does not move if the object is invalidated or inactivated.

      Multiple fields on an object can use this configuration in a Network instance. It is available on all sub-objects and relationship objects.

      If you change the Configuration, a dialog displays to confirm that you want to change the behavior for this primary.

  7. The Enabled? checkbox is selected by default.
  8. In the Visibility in Countries section, select a country and object for which this field will be available. A primary with the configuration Unique Checkbox is available for all sub-objects; Network Calculated primary type fields are available for addresses and parent HCOs only. Only one object can be chosen for a field.

    The following options are available when Unique Checkbox is configured:

    • Value - Chose a Default Value for the field. This value displays on the profile.
    • Required / Update - Select this checkbox to make it a required field.

    These options do not apply to the Network Calculated configuration. Also, NEX rulesClosedA user-defined rule applied to Network data loads which can be used to apply transformations to the data during the load. are not supported for Unique Checkbox or Network Calculated primary fields.

  9. Addresses only. When Address is chosen as the object for the primary field, a new setting called When to Calculate Primary Address displays in the Properties section. This setting does not display for any other object type. You can select any combination of the options to allow Network to calculate the primary for specific situations. For detailed information about these options, and examples of Network's primary calculation for the Unique Checkbox configuration, see Unique Checkbox with primary address calculations.

  10. In the Labels section, choose the Language and the Label for the custom field. The label displays on the profile page.
  11. Save your changes.

The custom field will now display on record profile pages.