Unique identifier for the call error entry, used internally by Veeva Vault to reference this specific record.

System-generated global identifier that uniquely identifies this call error record across all Vault environments.

Direct system link to the call error record, used for navigation or reference in Vault UI or API.

Descriptive name of the call error as recorded in the Vault system, typically aligned with the error type or message.

Current status of the call error record, such as Active, Inactive, or Resolved, depending on Vault's lifecycle configuration.

Username or system account that originally created this call error entry in Vault.

Date and time when the call error record was first created in the system.

Username or process that last modified the call error record.

Date and time when the call error entry was most recently updated in Vault.

Reference to the account associated with the failed or erroneous call, typically tied to a healthcare professional or organization.

Timestamp indicating when the original call event took place, prior to the error being logged.

Type or classification of the original call that resulted in an error, such as In-Person, Phone, or Virtual.

Explanation or root cause of the error, often derived from processing failures, validation errors, or missing data.

Raw XML payload or content associated with the call error, typically captured during data transmission or API interaction.

Vault user who executed the call or initiated the process that generated the error.

Internal Vault identifier for the record owner responsible for managing or resolving the call error.

Identifier from a legacy Customer Relationship Management (CRM) system that can have originated the call data, used for traceability or data migration tracking.