To configure network field mappings, users must have full permissions on the four mapping objects and their object types:

• network mapping, no object types
• network object mapping, no object types
• network field mapping, all object types
• network reference mapping, all object types

User permissions:

• Admins and integration users should have CRUD access to all four objects and their object types
• End users should have Read access to all objects and object types

Base Requirements

It is necessary to map the following:

• Vault CRM Org with Network instance
• Countries in Vault CRM and Network
• Data in Vault CRM with objects in Network
• Objects in Vault CRM with objects in Network

• Vault CRM object external ID with Network Entity ID need to be mapped. It is highly recommended for customers to map the CRM veeva_network_id__v field to the Network vid__v field.
• Vault CRM object external ID must be unique

• Standard and custom fields in Vault CRM with fields in Network
• Picklists and lookup values in Vault CRM with reference values in Network

Mapping is defined on the security profile level to provide the option to have different logic for various user groups and should be done before Vault CRM and Network communication.

Network Mappings section

The Network Mappings section of the admin page contains the following columns:

• Mapping Name (appended with the number of records in parentheses)
• description__v
• active__v
• country__v
• last_used_datetime__v
• The New Network Mapping action opens the Network Mapping Edit page to create a new mapping
• Click Edit to open the Network Mapping View page