Unique identifier for the Brick Hierarchy record, used as the primary key to distinguish each entry in the dataset.

System-generated global identifier used to uniquely reference the Brick Hierarchy record across the entire Veeva Vault environment.

Internal system link that references the specific Brick Hierarchy record within the platform for cross-record access or navigation.

User-defined name of the brick within the hierarchy, typically representing a geographic or organizational unit relevant to territory planning or segmentation.

Current lifecycle status of the Brick Hierarchy record, such as Active, Inactive, or Draft, used to indicate its availability or stage in the workflow.

Username or identifier of the user who originally created the Brick Hierarchy record in the system.

Timestamp indicating when the Brick Hierarchy record was first created, recorded in Vault's standard date-time format.

Username or identifier of the user who last updated the Brick Hierarchy record.

Timestamp of the most recent modification made to the Brick Hierarchy record, allowing for version tracking and auditability.

Identifier of the parent brick in the hierarchy, establishing a nested structure that supports multi-level territory management.

Vault user or group responsible for managing the Brick Hierarchy record, often used for security, reporting, and workflow routing.

Identifier imported from a legacy Customer Relationship Management (CRM) system, retained for mapping historical records or ensuring backward compatibility during system migration.