DATA SHARE RELEASE
JULY 23, 2026 — FIELD DETAILS
This article lists every view and column added to the ServiceCore Data Share on July 23, 2026, along with each field’s data type and whether it allows null values. For a high-level summary of this release, see the 07/21/2026, Data Share Updates, Fixes release notes article.
NEW VIEWS
VW_MESSAGE_TEMPLATE (New view)
Shows the reusable message subjects and bodies your team has created for automated customer communications.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| COMPANY_ID | NUMBER(38,0) | No | |
| NAME | VARCHAR(255) | Yes | |
| SUBJECT | VARCHAR(255) | No | |
| BODY | VARCHAR(16777216) | No | |
| DELETED_AT | TIMESTAMP_NTZ(9) | Yes | |
| CREATED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_BY_ID | NUMBER(38,0) | Yes |
VW_PLANNED_ROUTE (New view)
Shows each job on a route in one place, including the assigned driver, timing and duration, job type, product and quantity, location, and territory. This is the same data behind the "Planned Route" Standard Report in ServiceCore.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| COMPANY_ID | NUMBER(38,0) | No | |
| DRIVER_ID | NUMBER(38,0) | Yes | |
| DRIVER_FIRST_NAME | VARCHAR(63) | Yes | |
| DRIVER_LAST_NAME | VARCHAR(63) | Yes | |
| JOB_ID | NUMBER(38,0) | No | |
| JOB_DOC_NUMBER | VARCHAR(32) | Yes | |
| JOB_SCHEDULED_AT | DATE | Yes | |
| JOB_STARTS_AT | TIMESTAMP_NTZ(9) | Yes | |
| JOB_STARTED_AT | TIMESTAMP_NTZ(9) | Yes | |
| JOB_COMPLETED_AT | TIMESTAMP_NTZ(9) | Yes | |
| JOB_DURATION | NUMBER(38,0) | Yes | |
| JOB_SERVICE_DURATION | NUMBER(38,0) | Yes | |
| JOB_SCHEDULE_WEIGHT | NUMBER(38,0) | No | |
| RENTAL_ID | NUMBER(38,0) | Yes | |
| JOB_TYPE_ID | NUMBER(38,0) | Yes | |
| JOB_TYPE_NAME | VARCHAR(255) | Yes | |
| JOB_TYPE_IS_CONSUMING | NUMBER(38,0) | Yes | |
| JOB_TYPE_IS_PRODUCING | NUMBER(38,0) | Yes | |
| IS_SERVICE_JOB | NUMBER(1,0) | No | |
| IS_DELIVERY_JOB | NUMBER(1,0) | No | |
| IS_PICKUP_JOB | NUMBER(1,0) | No | |
| IS_EXCHANGE_JOB | NUMBER(1,0) | No | |
| IS_DESTINATION_JOB | NUMBER(1,0) | No | |
| PRODUCT_ID | NUMBER(38,0) | Yes | |
| QUANTITY | NUMBER(38,0) | Yes | |
| LATITUDE | NUMBER(18,12) | Yes | |
| LONGITUDE | NUMBER(18,12) | Yes | |
| SOURCE_LATITUDE | VARCHAR(16777216) | Yes | |
| SOURCE_LONGITUDE | VARCHAR(16777216) | Yes | |
| DISTANCE_IN_MILES | VARCHAR(16777216) | Yes | |
| JOB_CANCELED_AT | TIMESTAMP_NTZ(9) | Yes | |
| JOB_STATUS | VARCHAR(31) | Yes | |
| SITE_ID | NUMBER(38,0) | Yes | |
| TERRITORY_ID | NUMBER(38,0) | Yes | |
| DIVISION_ID | NUMBER(38,0) | Yes | |
| TERRITORY_NAME | VARCHAR(127) | Yes |
Workflow-Related Views
These views are tied to an upcoming ServiceCore feature and may return no rows until that feature is available in your account.
VW_WORKFLOW (New view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| NAME | VARCHAR(255) | No | |
| TRIGGER_TYPE | VARCHAR(50) | Yes | |
| DELETED_AT | TIMESTAMP_NTZ(9) | Yes | |
| COMPANY_ID | NUMBER(38,0) | No | |
| CREATED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_BY_ID | NUMBER(38,0) | Yes |
VW_WORKFLOW_VERSION (New view)
Tracks each revision of a workflow, its status, whether it requires a signature, and any generated document.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| WORKFLOW_ID | NUMBER(38,0) | No | |
| STATUS | VARCHAR(50) | Yes | |
| REQUIRES_SIGNATURE | BOOLEAN | Yes | |
| PDF_FILE_ID | NUMBER(38,0) | Yes | |
| PARENT_VERSION_ID | NUMBER(38,0) | Yes | |
| COMPANY_ID | NUMBER(38,0) | No | |
| CREATED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_AT | TIMESTAMP_NTZ(9) | Yes | |
| MODIFIED_BY_ID | NUMBER(38,0) | Yes |
VW_WORKFLOW_FIELD_DEFINITION (New view)
The standard field catalog (like Customer Name and Site Address) that custom workflow fields can map to.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| LABEL | VARCHAR(255) | No | |
| MAPPING_KEY | VARCHAR(255) | No | |
| FIELD_TYPE | VARCHAR(50) | No | |
| UNIT | VARCHAR(50) | Yes |
VW_WORKFLOW_FIELD (New view)
The fields configured on each workflow version, including custom fields and their required/conditional settings.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| WORKFLOW_VERSION_ID | NUMBER(38,0) | No | |
| FIELD_DEFINITION_ID | NUMBER(38,0) | Yes | |
| LABEL | VARCHAR(255) | Yes | |
| FIELD_TYPE | VARCHAR(50) | Yes | |
| UNIT | VARCHAR(50) | Yes | |
| IS_REQUIRED | BOOLEAN | Yes | |
| CONDITION_LOGIC | VARCHAR(50) | Yes |
VW_WORKFLOW_FIELD_ENUM_OPTION (New view)
The dropdown/enum options configured for custom workflow fields.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| WORKFLOW_FIELD_ID | NUMBER(38,0) | No | |
| VALUE | VARCHAR(255) | No | |
| SORT_ORDER | NUMBER(38,0) | Yes |
VW_PDF_FIELD_PLACEMENT (New view)
Where each workflow field is placed on the generated PDF document.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| ID | NUMBER(38,0) | No | |
| WORKFLOW_FIELD_ID | NUMBER(38,0) | No | |
| PAGE | NUMBER(38,0) | Yes | |
| X | FLOAT | No | |
| Y | FLOAT | No | |
| WIDTH | FLOAT | No | |
| HEIGHT | FLOAT | No | |
| FIELD_ENUM_OPTION_ID | NUMBER(38,0) | Yes | |
| BOOLEAN_OPTION | BOOLEAN | Yes |
VW_WORKFLOW_VERSION_JOB_TYPE (New view)
Which job types each workflow version applies to.
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| WORKFLOW_VERSION_ID | NUMBER(38,0) | No | |
| JOB_TYPE_ID | NUMBER(38,0) | No |
UPDATED VIEWS
VW_PAYMENT_GATEWAY_TOKEN_CARD (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| CAU_STATUS | VARCHAR(20) | Yes | Latest auto-refresh result the card network reported for a stored card. |
| CAU_UPDATED_AT | TIMESTAMP_NTZ(9) | Yes | When the card's CAU status was last updated. |
| DELETED_AT | TIMESTAMP_NTZ(9) | Yes | Marks which stored cards have been retired and shouldn't be used for new charges. |
VW_COMPANY_PREFERENCE (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| BILLING_TYPE | VARCHAR(31) | Yes | Default billing cadence at the company level. |
| INTERVAL_TYPE | VARCHAR(16) | Yes | Unit used for recurring billing at the company level. |
| INTERVAL_AMOUNT | NUMBER(38,0) | Yes | Length of the default recurring billing cycle at the company level. |
VW_CUSTOMER (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| BILLING_TYPE | VARCHAR(31) | Yes | Default billing cadence at the customer level. |
| INTERVAL_TYPE | VARCHAR(16) | Yes | Unit used for recurring billing at the customer level. |
| INTERVAL_AMOUNT | NUMBER(38,0) | Yes | Length of the default recurring billing cycle at the customer level. |
VW_TRANSACTION_LINE_ITEM (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| LINE_NUMBER | NUMBER(38,0) | Yes | Order in which line items appear on each transaction. |
VW_MESSAGING_AUTOMATION (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| USE_RECOMMENDED_NEXT_CLEANING | BOOLEAN | Yes | Whether reminders are anchored to the job's recommended next cleaning date. |
| MESSAGE_TEMPLATE_ID | NUMBER(38,0) | Yes | Links to the message template the automation uses. |
| CREATE_REMINDERS_FOR_PAST_JOBS | BOOLEAN | Yes | Whether the automation also creates reminders for jobs already in the past. |
| EXCLUDED_JOB_IDS | VARCHAR | Yes | Job IDs left out of the automation. |
VW_SCHEDULED_REMINDER (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| OVERRIDE_SUBJECT | VARCHAR(255) | Yes | Custom subject line, if one is set on the reminder. |
| OVERRIDE_BODY | VARCHAR | Yes | Custom message text, if one is set on the reminder. |
VW_CUSTOMER_STATS (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| OVERDUE_DATE | TIMESTAMP_NTZ(9) | Yes |
VW_BATCH_BILLING_OPERATION (Updated view)
| Column | Data Type | Allows Null | Notes |
|---|---|---|---|
| IN_FLIGHT_GROUP_KEY | VARCHAR(64) | Yes | Groups billing operations processed together in the same batch run. |