To configure this feature:

1. Ensure Configuring Accounts is complete.
2. Navigate to Business Admin > Objects > Veeva Settings.

3. Populate the enable_country_dimension__v Veeva Setting with a value of 1 at the Vault level. The default value is 0, which means transactional activity is not tracked by country.

   This setting enables the feature for all users in the Vault. Profile-level enablement is not supported.

4. Navigate to Business Admin > Objects.

5. Populate the country_code__v field on the account__v object and/or the country_code__v field on the user__sys object.

Optional Configuration

To enable users to override the field values listed for the objects in the following table:

1. Navigate to Admin > Users & Groups > Permission Sets.
2. Select the appropriate permission set.
3. Select the Objects tab.

4. Grant the following permissions: 

   Object	Object Permission	Object Type	Fields	Field Permission
   account__v	CRE	All applicable object types	country__v	Edit
   call2__v	CRE	All applicable object types	country_account__v country_user__v	Edit
   em_event__v	CRE	All applicable object types	country_user__v	Edit
   inventory_monitoring__v	CRE	All applicable object types	country_account__v	Edit
   medical_inquiry__v	CRE	All applicable object types	country_account__v	Edit
   medical_insight__v	CRE	All applicable object types	country_account__v country_user__v	Edit
   multichannel_activity__v	CRE	All applicable object types	country_account__v country_user__v	Edit
   order__v	CRE	All applicable object types	country_account__v country_user__v	Edit
   remote_meeting__v	CRE	All applicable object types	country_user__v	Edit
   sent_email__v	CRE	All applicable object types	country_account__v country_user__v	Edit
   user__sys	CRE	All	country__v	Edit

5. Navigate to Admin > Configuration > Objects.

6. Place the country_v field on the appropriate account__v and user__sys layouts.

7. Place the country_user__v field and the country_account__v field on the appropriate object layouts.

   Refer to the table above for a list of applicable objects.

All objects listed in the table above are enabled for stamping and use the following shared stamping logic:

• Shared stamping logic retrieves the value from the country_code__v field on the User object from the Owner field on the stamped object. For example, when a user records a call, the country_user__v field on the call2__v record is set to US if the country_code__v field on the call owner's User record is set to US. In this case, the correct User record to pull the country code from is identified from the Owner field on the call report.
• Shared stamping logic retrieves the value from the country_code__v field on the Account object from the account__v field in the stamped object. For example, if a user records a call for a German physician, the country_account__v field on the call2__v record is set to DE because the country_code__v field on the HCP’s Account record is set to DE. In this case, the correct User record to pull the country code from is identified from the account__v field on the call report.

To view activity by country, business admin users can create a report grouping records by the country_account__v field. This report gives the business admin a clear understanding of the activity distribution by country. For information on creating reports, see What are Reports?

When a user creates a transactional record, Vault CRM automatically stamps the country value on the record, unless the user enters a country value manually.

When a user edits an existing transactional record, Vault CRM only stamps the value if the field is not already populated, to avoid overwriting any manually-entered data. The value initially stamped on the transactional record is retained unless a user updates the country value in subsequent record edits.

If a user manually clears the country value by selecting None, Vault CRM retrieves the country value and stamps it on the record.