This article provides an overview of all the Filevine (FV) objects and Data Warehouse (DW) tables that are compatible with the audit process. It outlines two key components:
-
Audit IDs:
Primary keys are required for each Filevine report. -
Audit Values:
Specific fields that must be included to ensure accurate data comparison during audits.
Supported Fields
The audit process supports fields related to Contacts, Documents, Notes, and Projects. Each category below lists the compatible fields used for validation.
The values on the right shows how the fields are named in the Data Warehouse (using CamelCase), while the column on the left shows how they appear in the Filevine UI.
-
Supported Contact Fields
Supported | |
"First Name": "firstName" | ✅ |
"Middle Name": "middleName" | ✅ |
"Last Name": "lastName" | ✅ |
"Nickname": "nickname" | ✅ |
"Full Name": "fullName" | ✅ |
"Email 1": "primaryEmail" | ✅ |
"Date of Birth": "birthDate" | ✅ |
"Date of Death": "deathDate" | ✅ |
"Company Name": "fromCompany" | ✅ |
"Phones": "phones" | ✅ |
"Emails": "emails" | ✅ |
"Prefix": "prefix" | ✅ |
"Suffix": "suffix" | ✅ |
"Salutation": "salutation" | ✅ |
"Hashtags": "hashtags" | ✅ |
"Job Title": "jobTitle" | ✅ |
"Department": "department" | ✅ |
"is Deceased": "isDeceased" | ✅ |
"SSN": "ssn" | ✅ |
"Notes": "notes" | ✅ |
"Gender": "gender" | ✅ |
"Language": "language" | ✅ |
"Marital Status": "maritalStatus" | ✅ |
"Drivers License Number": "driversLicenseNumber" | ✅ |
"Fiduciary": "fiduciary" | ✅ |
"is a Minor": "isMinor" | ✅ |
"Remarket": "remarket" | ✅ |
"Bar Number": "barNumber" | ✅ |
"is Texting Permitted": "isTextingPermitted" | ✅ |
"Specialty": "specialty" | ✅ |
-
Supported Document Fields
Here you will find all the document-related fields that are checked and validated during audits.
"Filename": "filename" | ✅ |
"Size (Bytes)": "size" | ✅ |
"Uploaded By Name": "uploaderFullname" | ✅ |
"Upload Date": "uploadDate" | ✅ |
"Doc Hashtags": "hashtags" | ✅ |
-
Supported Note Fields
This table lists the fields related to notes that are supported during the audit process.
"Note Type": "typeTag" | ✅ |
"Note text": "body" | ✅ |
"Created At": "createdAt" | ✅ |
"Last Activity": "lastActivity" | ✅ |
"Pinned to Project": "isPinnedToProject" | ✅ |
"Pinned to My Feed": "isPinnedToFeed" | ✅ |
-
Supported Project Fields
This is a list of all fields related to projects that are recognized and used during audits.
"Name": "projectName" | ✅ |
"Client Person Id": "clientId" | ✅ |
"Create Date": "createdDate" | ✅ |
"Phase": "phaseName" | ✅ |
"Client Full Name": "clientName" | ✅ |
"First Primary": "firstPrimaryName" | ✅ |
"Last Activity": "lastActivity" | ✅ |
"Email Address": "uniqueKey" | ✅ |
"Name": "projectOrClientName" | ✅ |
"Hashtags": "hashtags" | ✅ |
"Email Address": "projectEmailAddress" | ✅ |
"Filevine URL": "projectUrl" | ✅ |
"Phase Date": "phaseDate" | ✅ |
"Incident Date": "incidentDate" | ✅ |
Supported Collections
This table lists all the collections that are currently supported by the audit process.
Field Type Group | Field Use | Field type | FV CSV Report Data Type | DW Data Type | Supported |
Amount | Amount fields are best suited for data that use only numerals and are consistent across projects. |
|
Numeric | Numeric | ✅ |
Text | Text fields should only be used for data that requires text and varies greatly from project to project. |
|
Text | Text | ✅ |
Yes/No | Filevine Support recommends that Yes/No fields be used in cases where a “Yes” or “No” answer is required. |
|
Boolean |
Boolean | ✅ |
Dropdown List and Multi-Select Lists | Multiple choice fields are best suited for information that has several possible answers. |
|
Text | Text | ✅ |
Url | Url fields are used when you need to include a link to another webpage within a project. |
|
Text | Text | ✅ |
Case Number and Incident Date | Special fields like case number and incident date fields are used in very specific circumstances. |
|
Text | Text | ✅ |
Others |
|
'jsonb' | ✅ |
Comments
0 comments
Please sign in to leave a comment.