Network Field Mapping
Use the Network Field Mapping page to establish a relationship between a Network Field and a Vault CRM Field.
Who can use this feature?
- System Admin Users — Browser
- Mapping Network Fields
- Users do not require an additional license
Configuring Network Field Mapping for
System Admin Users
Ensure Configuring Accounts is complete.
Mapping Network Fields as
System Admin Users
The Network Field Mapping screen enables system admin users to establish a relationship between a Network Field and a Vault CRM Field.
- Network Field API Name is a picklist of Field Names available on the Network Object
- Vault CRM Object API Name is a picklist of Field Names within the Vault CRM Object
- Object Type is automatically defined depending on the values that have been selected in Network Field API Name and Vault CRM Field API Name
- The Save action saves the Object Mapping. After saving the mapping, select the Validate Vault CRM Bridge button in Network to validate the mappings. For more information, see Validate the Vault CRM Bridge.
- The Cancel action cancels the mapping
Default Object Types for HCP and HCO can be set by populating the Network Setting field Default HCP Object and Default HCO Object Type.
Multi-value picklists are supported for network field mappings.
Special Field Mapping
The following three groups of fields are implicitly mapped; do not create field mapping for these fields:
- record_state__v field in Network
- customer_master_status__v in Vault CRM
- All fields related to License
All Integration users and end users should have permission to the customer_master_status__v field. This field is mapped to the record_state__v field implicitly. The general logic is as follows:
| record_state__v | customer_master_status__v |
|---|---|
| VALID | valid__v |
| UNDER_REVIEW | under_review__v |
|
rejected__v |
The customer_master_status__v field could also have a value of inactive__v if the Inactive Network Records feature is enabled.
Fields
|
Field Label |
Field Name |
Data Type |
Description |
Size |
Required? |
|---|---|---|---|---|---|
|
Field Mapping ID |
name__v |
Auto Number |
Network field mapping ID |
|
Yes |
|
Network Object Mapping |
network_object_mapping__v |
Parent Object (Network Object Mapping) |
Link to Network Object Mapping |
|
Yes |
|
Vault CRM Field API Name |
crm_field_api_name__v |
Text |
Vault CRM field API name |
43 |
No |
|
Network Field API Name |
network_field_api_name__v |
Text |
Network field API name |
255 |
Yes |
|
Lookup ID API Name |
lookup_id_api_name__v |
Text |
Vault CRM lookup object ID field API name |
43 |
No |
|
Object Mapping Reference |
object_mapping_reference__v |
Lookup (Network Object Mapping) |
Link to child Object Mapping |
|
No |
Field Usage Depending on Object Type
| Field Label | name__v | lookup__v | picklist__v | record_type__v | object_reference__v | external_id__v |
|---|---|---|---|---|---|---|
| Field Mapping ID | Yes | Yes | Yes | Yes | Yes | Yes |
| Network Object Mapping | Yes | Yes | Yes | Yes | Yes | Yes |
| Vault CRM Field API Name | Yes | Yes | Yes | Yes | Yes | |
| Network Field API Name | Yes | Yes | Yes | Yes | Yes | Yes |
| Lookup ID API Name | No | Yes | No | No | ||
| Object Mapping Reference | No | No | No | No | Yes | Yes |
| Unique Key | Yes | Yes | Yes | Yes | Yes | Yes |
