Veeva Vault

Veeva Vault is a comprehensive data management system designed to streamline the collection, cleaning, and reporting of clinical trial data.

Features

Feature Name	Supported	Notes
Capture deletes		Only for the source tables that support the delete operation.
History mode
Custom data		Custom objects and fields
Data blocking		Column level, table level, and schema level
Column hashing
Re-sync		Connection level and table level
Row filtering
API configurable		API configuration
Priority-first sync		`DOCUMENTS` table and the tables that contain the `modified_date__v` column.
Fivetran data models
Private networking
Authorization via API

Setup guide

Follow our step-by-step Veeva Vault setup guide to connect Veeva Vault with your destination using Fivetran connectors.

Sync overview

We incrementally sync the tables that have the modified_date__v column in the source.

We re-import the remaining tables daily.

To capture deletes for incremental tables, we use the deletions API for all source tables that support it.

Document metadata and picklist data syncing

We sync both document metadata and picklist data from Veeva Vault. To retrieve human-readable labels (values) for picklist columns in your tables, join your data tables with the PICKLIST, PICKLIST_USED_IN, and PICKLIST_VALUES tables.

Fivetran applies naming transformations to table and column names as part of Fivetran naming conventions. We add additional columns to the picklist-related tables to match the names in your destination and simplify the joins.

Mapping for joins

Use the following renamed columns to enable accurate joins between your source tables and PICKLIST tables:

Table	Original column	Fivetran renamed column
`PICKLIST`	`name`	`renamed_column_name`
`PICKLIST_USED_IN`	`object_name`	`renamed_object_name`
`PICKLIST_USED_IN`	`property_name`	`renamed_property_name`
`PICKLIST_USED_IN`	`document_type_name`	`renamed_document_type_name`

To retrieve the display values for each picklist, join your data tables with the PICKLIST and PICKLIST_VALUES tables using the updated column names.

Schema information

This schema diagram illustrates how objects relate to one another. It is not a complete Entity Relationship Diagram. It shows relationships for some central entities and workflows. Many standard and all custom entities that are delivered by Veeva Vault connections are omitted for brevity.

To zoom, open the ERD in a new window.

Unstructured file replication Beta

We support the unstructured file replication feature only in our SaaS Deployment model.

The Veeva Vault connector supports unstructured file replication. Fivetran applies the following rules while syncing unstructured files:

We validate the records within the DOCUMENTS table and only sync the latest records.
We prefix each value within the file_name column with the value in the version_id column. For example, if the version id is 1111_0_1 and the filename is Profile Labeling Document 1. docx, then we update the name as 1111_0_1__Profile Labeling Document 1.docx in the _fivetran_file_path column in your destination.
We sync only the viewable rendition of each file. If a viewable rendition is not available, we sync the original file.
The _fivetran_file_path column stores the relative source path and reference to the respective file’s location in the destination.

Limitations

We do not capture deletes for Documents or their associated files. We only capture creations and updates to existing files and version changes.

File syncing is not supported for connections using Hybrid Deployment.