Unique identifier for the analytics file record in the Vault system.

System-generated global identifier used to uniquely identify the record across environments and integrations.

System-generated internal Vault link used for navigating directly to the analytics file within the Vault platform.

Internal Veeva Vault name used to reference the file in the system, which is not necessarily the same as the display file name.

Current lifecycle status of the analytics file, reflecting where it stands in processing or validation.

Username of the user who originally uploaded or created the analytics file.

Timestamp indicating when the analytics file was initially created in the system.

Username of the user who last modified the analytics file record.

Timestamp reflecting the most recent update to the analytics file metadata or content.

Path or storage location identifier where the file is hosted within the analytics repository.

Numeric value representing the number of segment buckets defined for data classification in the file.

Primary label used in reports to identify the first major data column in the analytics file.

Indicates whether the file includes predefined sales or performance goals (true or false).

The date associated with the data snapshot contained in the file. This is used for reporting alignment.

Reference to the data mapping template that defines how columns in the file map to standardized fields.

Timestamp marking when the file was last processed through the analytics pipeline.

Defines how many decimal places should be applied when displaying numeric metrics from the file.

Flag indicating if this file should be included in market-level sales analysis reporting (true or false).

Indicates whether error reporting is enabled for this file's data validation process (true or false).

FTP username associated with the account used to upload the file into the Vault system.

The original or user-defined name of the uploaded file, typically visible in the Vault UI.

Label indicating whether the file includes formulary-related data relevant to field representatives.

Type of incremental load (such as 'append', 'update', or 'overwrite') used when ingesting this data file.

Boolean flag indicating whether the data file is part of an incremental load process (true or false).

Comma-separated list of fields in the file that have been successfully mapped to standard Vault schema fields.

Indicates whether market-level mapping has been completed for the data within the file (true or false).

Flag that, when true, allows override of the default account threshold during data import or analysis.

Indicates whether payer or plan-level mappings have been applied to the data (true or false).

Total number of data rows contained in the uploaded file.

Unit of measure or multiplier used to normalize numeric values, such as 'units', 'thousands', or 'millions'.

Secondary label used in reports to represent a second major metric or classification in the file.

Boolean value indicating whether simplified indexing logic is applied to speed up data access or reporting.

Status field showing the current processing state of the file in the analytics workflow.

Boolean flag showing whether territory-level identifiers or labels are present in the data file.

Category or classification of the file, such as 'sales', 'call activity', or 'formulary'.

Identifies the market or therapeutic area that the file data pertains to.

User or team that owns the file record and is responsible for its accuracy and management.

Reference identifier used to map the analytics file back to a corresponding record in a legacy Customer Relationship Management (CRM) system.