Vault CRM integrations
Validate Vault CRM bridge
The Validate Vault CRM Bridge job checks the mappings between Network and Vault CRM. The validation is extended to identify additional mapping and common configuration issues, for example, picklist and field dependencies for Vault CRM object types.
In addition, the validation file that you can download after the job completes includes an additional sheet, Configuration issues, to help you identify the issues to fix.
About the validation job
The Validate Vault CRM Bridge job runs on the first day of each month for all active Vault CRM Bridge configurations.
To review the report:
-
In the Admin console, click System Interfaces > Network Bridge and click Validate Vault CRM Bridge.
-
Click Download beside the latest job to save the file and review.
The file identifies issues and provides or suggests ways to fix them.
Administrators can run the job at any time.
For details, see Validate the Vault CRM Bridge in the Veeva Network Online Help.
Additional mapping checks
The Network Bridge validation now checks for the following mapping issues. The issues are identified on the sheets in the .xslx file that you download after the job runs.
| Mapping | Check | Validation Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Vault CRM status__v field | Ensure that there are no Network Field Mappings for the Vault CRM status__v field. | Network Field Mapping sheet
Cannot map to Vault CRM status__v (bulk updates not supported). |
||||||||
| Network Address Inheritance fields |
If any Network Address Inheritance field is mapped to a CRM field, check that all three required Network fields are mapped.
|
Network Field Mapping sheet
Vault CRM address inheritance requires 3 mapped fields. Missing: {crm fields missing}. |
||||||||
| Formula fields |
Ensure there are no mappings to Vault CRM formula fields.
For example, some CDA fields are formula fields. |
Network Field Mapping sheet
Cannot map to Vault formula field {crm field name}; Network cannot update formulas. |
||||||||
| Boolean reference values | Ensure that the standard boolean values are mapped. | Missing Network Ref. Mapping sheet
Provides the standard mapping.
|
||||||||
| External ID | Ensure the object_reference_mapping__v field is populated for External ID field mappings. | Network Field Mapping sheet
Referenced object mapping does not exist. |
Configuration checks
The Network Bridge validation now checks for the following common configuration issues.
| Confguration | Check | Validation Notes |
|---|---|---|
| Vault CRM Integration user validation | ||
| Integration user - Network Admin |
Ensure the Vault CRM Integration user is set as the Network Admin.
The Network Admin field on the Integration user must be selected. |
Network Mapping sheet CRM integration user's 'Network Admin' field is false; set it to true. |
| Integration user - Countries |
Ensure the Vault CRM Integration user has all the mapped countries listed in the user's Network Additional Countries field.
All mapped countries need to be included in the Network Additional Countries field on the user account. |
Network Mapping sheet The CRM integration user's 'Network Additional Countries' field requires all mapped countries. Add these countries: {list of missing countries}. |
| Object Type validations | ||
| HCP and HCO Object Types |
Ensure the Default HCP and HCO Object Types are populated in Vault CRM.
On the network_settings__v record, check if the following fields have values:
|
Network Object Mapping sheet
Default HCP/HCO Object Types are not configured in Vault CRM Network Settings. Please update. |
| Object Type -Field |
Ensure all mapped fields are available for the object types used in the integration.
Relevant object types are determined by the default HCP and HCO in the Network Settings in addition to any object types included in a field mapping to the object_type__v field. |
Network Field Mapping sheet Field is not available for object types, see Configuration Issues sheet. |
| Object Type - Picklist Values |
Ensure all mapped picklist field values are available for the object types used in the integration.
Relevant object types are determined by the default HCP and HCO in the Network Settings in addition to any object types included in a field mapping to the object_type__v field. Only check Network codes that are active for the mapped countries. |
Network Reference Mapping sheet
Picklist value is not available for object types, see Configuration Issues sheet. The Configuration Issues sheet identifies the picklists that should be added or removed for the object type for each country. |
| Picklist dependency validations | ||
| Country dependencies |
Check that country-specific picklist dependencies are configured in Vault CRM for mapped picklist values.
The check is only done for picklist fields in CRM where the controlling field is the same field that is mapped to primary_country__v (HCP/HCO) or country__v (Address) in Network. Check only for mapped countries. |
Network Reference Mapping sheet
Incorrect picklist dependencies, see Configuration Issues sheet. |
| Data Change Request Results |
Ensure all picklist values for the Results field are enabled for the three object types on the on the Data Change Request object:
|
Network Reference Mapping sheet
If there are any issues, see the Configuration Issues sheet. |
| Valid Network Reference Code | Reference codes are no longer marked invalid if they are present but are not used in a mapped country. | Network Reference Mapping sheet
Picklists that are mapped but are not used by a mapped country are marked as Valid. Picklists are marked invalid if they are used by a mapped country but are not active in Network. |
Bridge validation file
The following changes have been made to the file that you can download after the validation runs.
Configuration Issues sheet
A new sheet is added to the file to identify the following Vault CRM configuration issues:
-
Picklist Dependency
-
Object Type - Field
-
Object Type - Picklist Value
The Summary sheet displays a count of Configuration Issue types.
Vault CRM Bridge record counts
Network Administrators can now see the number of unchanged records that were upserted to Vault CRM in a bridge job. The counts for records added and updated have also been enhanced so they more accurately reflect the data.
This enhancement is enabled by default.
Job details
After a Vault CRM Bridge job runs, the Bridge Summary on the Job Details page displays a count of records that were added, updated, and had errors.
The Unchanged column is added to the table.
-
Adds - Upserted records were created in Vault CRM.
-
Updates - Upserted records were updated in Vault CRM.
-
Errors - Records failed to be upserted to Vault CRM.
Click Download Error Report Log for details.
-
Unchanged - Records were upserted to Vault CRM but did not contain changes.
Report on upserted records
Advanced reporting users can report on the data from the Bridge Summary. In the SQL Query Editor (Reports), the Job Stats table is updated to include unchanged records.
Example query
Use this query to understand the impact of a bridge job.
SELECT
job.job_id,
job.job_type,
job.subscription,
RIGHT( job.subscription, 2 ) AS "country",
job.job_system,
job.status,
job.start_time,
job_stats_summary. "hco.adds",
job_stats_summary. "hco.updates",
job_stats_summary. "hco.unchanged",
job_stats_summary. "hco.errors",
job_stats_summary. "hcp.adds",
job_stats_summary. "hcp.updates",
job_stats_summary. "hcp.unchanged",
job_stats_summary. "hcp.errors",
job_stats_summary. "address.adds",
job_stats_summary. "address.updates",
job_stats_summary. "address.unchanged",
job_stats_summary. "address.errors",
job_stats_summary. "parenthco.adds",
job_stats_summary. "parenthco.updates",
job_stats_summary. "parenthco.unchanged",
job_stats_summary. "parenthco.errors"
FROM
job LEFT JOIN (
-- This optimized subquery now also pivots the error metrics
SELECT
job_id,
-- HCO
SUM (
CASE
WHEN metric = 'hco.adds'
THEN counter
ELSE 0
END
) AS "hco.adds",
SUM (
CASE
WHEN metric = 'hco.updates'
THEN counter
ELSE 0
END
) AS "hco.updates",
SUM (
CASE
WHEN metric = 'hco.unchanged'
THEN counter
ELSE 0
END
) AS "hco.unchanged",
SUM (
CASE
WHEN metric = 'hco.errors'
THEN counter
ELSE 0
END
) AS "hco.errors",
-- HCP
SUM (
CASE
WHEN metric = 'hcp.adds'
THEN counter
ELSE 0
END
) AS "hcp.adds",
SUM (
CASE
WHEN metric = 'hcp.updates'
THEN counter
ELSE 0
END
) AS "hcp.updates",
SUM (
CASE
WHEN metric = 'hcp.unchanged'
THEN counter
ELSE 0
END
) AS "hcp.unchanged",
SUM (
CASE
WHEN metric = 'hcp.errors'
THEN counter
ELSE 0
END
) AS "hcp.errors",
-- Address
SUM (
CASE
WHEN metric = 'address.adds'
THEN counter
ELSE 0
END
) AS "address.adds",
SUM (
CASE
WHEN metric = 'address.updates'
THEN counter
ELSE 0
END
) AS "address.updates",
SUM (
CASE
WHEN metric = 'address.unchanged'
THEN counter
ELSE 0
END
) AS "address.unchanged",
SUM (
CASE
WHEN metric = 'address.errors'
THEN counter
ELSE 0
END
) AS "address.errors",
-- ParentHCO
SUM (
CASE
WHEN metric = 'parenthco.adds'
THEN counter
ELSE 0
END
) AS "parenthco.adds",
SUM (
CASE
WHEN metric = 'parenthco.updates'
THEN counter
ELSE 0
END
) AS "parenthco.updates",
SUM (
CASE
WHEN metric = 'parenthco.unchanged'
THEN counter
ELSE 0
END
) AS "parenthco.unchanged",
SUM (
CASE
WHEN metric = 'parenthco.errors'
THEN counter
ELSE 0
END
) AS "parenthco.errors"
FROM
job_stats
GROUP BY
job_id
) AS job_stats_summary
ON job.job_id = job_stats_summary.job_id
WHERE
job.job_type = 'bridge'
AND datediff (
'hours',
job.end_time,
getdate ()) < 72
Example results
