Enabling data model fields
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 masterA 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__vfield 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:
- In the Admin console, click Data Model and select the Customer Master data domain.
- Open the object that the field is associated with.
- In the Fields section, click the field name; for example, the HCP
- On the Edit Field page, expand the Visibility in Countries section.
- In the Managed by Customer section, click Add Country Group.
- Choose the countries and objects that you want to manage and load your own data into. Set up any rules or other configuration requirements.
- Click Done.
- Complete any other changes and Save your changes.
- 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.
- 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 fields can be enabled or disabled (as a set).
(Note: These fields are not considered a set for Japan).
|All Address Lines (reporting only)||
|All Alternate Names||
|All Credentials||All fields in this group.|
|All Delivery Address Lines (reporting only)||
|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||
|All National IDs||
|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.|
Administrators and data managers can disable fields in the Network Data Model.
To disable a field:
- In the Admin console, click Data Model and select a data domain.
- Open the object that the field is associated with.
- In the Field section, click the field name to open the configuration page.
- 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<![CDATA[ ]]>, are enabled by default and cannot be disabled.
A message displays to remind you that the field data will become unavailable.
If the field is used for any profile validation rules, the message displays the affected rules. Disabled fields are not automatically removed from profile validation rules. Disable the rule or update the rule to remove the field. If a profile validation rule triggers for a disabled field, data stewards cannot fix the issue because the field no longer displays on the record.
- Click Disable this Field. The icon becomes Disabled .
Impact on Network features
- To learn how Network reports handle disabled fields, see Masking disabled fields.
- To understand how target subscriptions are impacted, see Considerations for disabled data model fields.