Enabling data model fields

AD
DM

Veeva OpenData fields can be enabled to load local or third party managed data. A field can be managed by Veeva in some countries, managed by a third party source in other countries, or be customer-managed in the remaining countries. If the Enable Multi Master Support option is enabled in your Network instance, a field can be managed by more than one masterClosed A customer instance can subscribe to more than one master for a specific country (for example, Veeva OpenData and a third party master), which allows routing of DCRs to the appropriate master data stewards. in a country.

When a subscription is enabled on the Veeva OpenData Subscription page in a Network instance, fields managed by Veeva OpenData in that country display in the Managed by a Master Data Source section on the Edit Field page. The rows in this section cannot be edited.

Third party managed fields are determined by third party systems listed on the System page. When a field is managed by a third party system for a country, the country is identified in the Managed by Customer section on the Edit Field page.

If a field is managed by multiple masters for a country, the country is listed in both sections. For example, if the first_name__v field is managed by both Veeva OpenData and a third party system for Andorra, Andorra is listed in the Managed by a Master Data Source and Managed by Customer section.

Data model fields used by all countries that do not have an Veeva OpenData subscription enabled are shown in the Managed by Customer section by default. An icon displays in the user interface to advise users that ownership of these fields will revert to Veeva OpenData when a Veeva OpenData subscription is enabled for a particular country.

Remove countries from fields

The Managed by Customer section can be edited for each data model field. However, countries cannot be removed from this section in the following situations:

  • When fields are managed by Veeva OpenData or third party systems for a country. An error occurs if users attempt to remove a third party managed country from the Managed by Customer section.
  • If the country is in the same master instance as a country that is enabled for Veeva OpenData.

    For example, if the nickname__v field is manged by Veeva OpenData for New Zealand, Australia cannot be removed from the Managed by Customer section because Australia and New Zealand belong to the same master instance. This ensures that if the country (for example, Australia) is later enabled for Veeva OpenData, it can be easily managed on the Data Model pages; it would be difficult to do if the country had been previously removed.

    When a country is attempted to be removed from a field, an error message explains why the changes cannot be saved: Cannot update master field data: <field_name>. Cannot remove countries that could potentially be managed by a master data source: <country>.

    If you remove a country from the Managed by Customer section and then later enable the Veeva OpenData subscription for that country, the field is now managed by Veeva OpenData. You can add the country back to the Managed by a Customer section. After the page is saved and reloaded, that country accurately displays in the Managed by a Master Data Source section.

Enable Veeva OpenData fields

To enable Veeva OpenData fields for local or third party data source:

  1. In the Admin console, click Data Model and select the Customer Master data domain.
  2. Open the object that the field is associated with.
  3. In the Fields section, click the field name; for example, the HCP credentials_1__v field.
  4. On the Edit Field page, expand the Visibility in Countries section.
  5. In the Managed by Customer section, click Add Country Group.

  6. Choose the countries and objects that you want to manage and load your own data into. Set up any rules or other configuration requirements.

    For details about field settings, see Creating custom fields.

  7. Click Done.
  8. Complete any other changes and Save your changes.
  9. On the object configuration page, find the field again and click the Disabled icon in the Status column. The icon changes to the Enabled icon to indicate that the field is now enabled.

The Veeva OpenData field is enabled and can be used to load customer or third party master data. Change requests for that field are automatically routed to the local data stewards, even if the record itself is owned by Veeva OpenData.

For information about enabling fields for Veeva OpenData to master, see Adding Veeva OpenData fields.

Enabling field sets

Typically, groups of fields are enabled or disabled as a set; if you enable one field, all of the fields in that set are also enabled. This helps to ensure data consistency and accuracy; for example, if the hcp_focus_area_3__v field is enabled but the other of the fields in the group are not, loading and managing data in that one field will be difficult and problematic for your data stewards.

If you enable or disable one field in a set of fields, a dialog displays so you can confirm or cancel the action.

Note: Only enabling or disabling one field in a group affects the entire set; other changes to a field in a set are contained to that field only.

Review the table below to understand the behavior for each set of fields.

Field Set Fields That Cannot Be Disabled Fields That Can Be Enabled / Disabled

All Accreditations

  

All fields can be enabled or disabled (as a set).

(Note: These fields are not considered a set for Japan).
All Address Lines (reporting only)   address_line_1__v through address_line_3__v
All Alternate Names alternate_name_1__v alternate_name_2__v through alternate_name_10__v (as a set)
All Credentials   All fields in this group.
All Delivery Address Lines (reporting only)   delivery_address_line__v through delivery_address_line_3__v
All Emails All fields in this group.  
All Faxes   All fields in this group.
All HCO Focus Areas   All fields can be enabled or disabled (as a set).
All HCP Focus Areas   All fields can be enabled or disabled (as a set).
All Medical Degrees

medical_degree_1__v and medical_degree_2__v (as a set)

medical_degree_3__v through medical_degree_5__v (as a set)
All National IDs

national_id__v (individual field)

national_id_2__v through national_id_5__v (as a set)
All Old CIP ID End Dates   All fields can be enabled or disabled (as a set).)
All Old CIP IDs   All fields can be enabled or disabled (as a set).
All Phones   All fields in this group.
All Specialties All fields in this group.  
All URLs   All fields in this group.

Inactivating fields

Administrators and Data Managers can inactivate fields in the Network Data Model.

Impact on Network features

Before inactivating a field, consider how it can affect other Network features:

  • Record profiles - Fields are not visible on profiles.

  • Field sets - Other fields in the set might also be inactivated.

  • Network hashtags - Hashtags that use the field in a rule will be automatically inactivated.

  • Profile validation rules - Rules that use the field will continue to run but the field will not be available on the profile so the issue cannot be fixed. Disable the rule or update the rule to remove the field.

  • Reports - Inactivated fields are masked in advanced report results. For more information, see Masking disabled fields.

  • Target subscriptions - Only enabled fields are exported. For more information, see Considerations for disabled data model fields.

Inactivate a field

  1. In the Admin console, click Data Model and select a data domain.
  2. Open the object that the field is associated with.
  3. In the Field section, click the field name to open the configuration page.
  4. Find the field and click the Enabled icon beside it. Fields that do not have the toggle icon and have the green checkmark instead, Enabled, are enabled by default and cannot be disabled.

    A message displays to remind you that the field data will become unavailable. Impacted features are also noted.

  5. Click Inactivate This Field. The icon becomes Disabled .