Skip to main content

Import Rules & Field Columns

Alex Hom avatar
Written by Alex Hom
Updated over 2 weeks ago

Rules

  1. All Jobs/Tasks must use their latest templates

  2. Inaccurate data within a row will cause the row to be skipped during processing

    1. Accurate data will still be processed normally

  3. Template column headers should NOT be reordered or modified

  4. Columns with ‘Blank’ values will NOT update when updating

System Columns
(These are default columns that are part of every template)

Column Name

Description

Example

jobDocumentId

A Job’s Document ID

ASSESS-77

jobExternalIdentifier

A unique name for reference to another system

ABC777

taskDocumentId

A Task’s Document ID

ASSESS-78

name

A required field for the name of the Job/Task

Permit 77

description

-

-

assigneeContactId

System ID of a Project User

(Reach out to a CSM liaison)

358

statusId

System ID of a Job/Task status

(Refer to Statuses within a Document Template)
(blank = New status)

189

assetShortCode

An over.vu’s Asset’s unique Code

-

assetExternalIdentifier

An over.vu’s Asset’s unique referential name

-

Field Columns
(These columns will follow the Document's Template)

Field Type

Rules

Example

Long Text

Data must be shorter than 4000 characters

“Text…”

Short Text

Data must be shorter than 250 characters

“Text…”

Boolean

Data must be entered as “TRUE” or “FALSE

“FALSE”

Date

Dates must be entered in the format
YYYY-MM-DD

“2025-02-14”

Single Select

Data must be case-sensitive to the field’s variables

“Option 1”

Multi Select

Data must be case-sensitive to field’s variables

(Separate multiple variables with a comma and no spaces, in any order)

“zZz,AAaAA,Option 1”

Contact Selector

Data must be entered as User ID # from over.vu

(Reach out to a CSM liaison)

-

Did this answer your question?