Summary
This release focuses on improving platform stability, streamlining schema management workflows, and enhancing user administration tools. Key updates include a new bulk schema editing interface, improved session timeout handling, and several fixes to deployment and schema management behavior.
Customer Access
The following updates will automatically be available to all customers next time they log into Zone Data Portal.
New Features & Improvements (2)
Platform Experience
Bulk Schema Creation via Text Input
Added a text-based input interface that allows users to create table schemas in bulk. Input must be provided in JSON format, enabling users to quickly define multiple fields and schema structures at once. This significantly reduces the time required to configure tables with many columns. (See additional details here.)
- What this means: Users can quickly define tables with many fields, significantly reducing the time required to configure new schemas.
Improved Timeout Handling
- Users were experiencing unexpected session timeouts during active sessions. We have optimized token refresh behavior to follow security best practices, ensuring user tokens are refreshed while the session remains active.
- What this means: Users should experience fewer unexpected timeouts and will be less likely to be forced to log in again during active use.
Customer Impacts
These updates improve the overall customer experience by reducing session interruptions and simplifying schema configuration workflows. The new bulk schema creation capability helps minimize manual entry and reduces the potential for configuration errors.
Product Maintenance & Fixes
Schema Management
Deployment Manager UI Fix
Resolved an issue where FlowTask changes were incorrectly displayed as Schema changes in the Deployment Manager.
Schema Change Grouping Fix
Fixed an edge case where editing columns across multiple schemas (e.g., Locations and Items) in the Deployment Manager caused all changes to be incorrectly grouped under the first edited schema.
Additional Details
JSON & TSQL Short Guide Tables
| Field | Description | Notes | Example |
| id | Unique column identifier | Do not include when creating a new field and do not update as this is system generated | 8840 |
| name | Display name of the column | "Customer Internal ID" | |
| type | Data type used by the schema | "Numeric" | |
| length | Character length (strings only) | 100 | 100 |
| precision | Total numeric digits | 20 | 20 |
| scale | Decimal digits | 2 | 2 |
| isIdentity | Whether column is auto-increment | Do not include when creating a new field and do not update as this is system generated | FALSE |
| primaryKey | Whether column is primary key | TRUE |
| If T-SQL Column Is | JSON Represents |
| NVARCHAR(100) | "type": "NVarChar", "length": 100 |
| NUMERIC(38,0) | "type": "Numeric", "precision": 38, "scale": 0 |
| DECIMAL(19,2) | "type": "Decimal", "precision": 19, "scale": 2 |
| DATE | "type": "Date" |
| DATETIME2(7) | "type": "DateTime2", "scale": 7 |
| T-SQL Data Type | JSON Type | JSON Length | JSON Precision | JSON Scale | Example JSON |
| NVARCHAR(n) | NVarChar | n | 0 | 0 | { "type": "NVarChar", "length": 100 } |
| NVARCHAR(MAX) | NVarChar | 4000* | 0 | 0 | { "type": "NVarChar", "length": 4000 } |
| NUMERIC(p,s) | Numeric | 0 | p | s | { "type": "Numeric", "precision": 20, "scale": 2 } |
| DECIMAL(p,s) | Decimal | 0 | p | s | { "type": "Decimal", "precision": 19, "scale": 2 } |
| INT | Numeric | 0 | 10 | 0 | { "type": "Numeric", "precision": 10, "scale": 0 } |
| BIGINT | Numeric | 0 | 19 | 0 | { "type": "Numeric", "precision": 19, "scale": 0 } |
| DATE | Date | 0 | 0 | 0 | { "type": "Date" } |
| DATETIME2(s) | DateTime2 | 0 | 0 | s | { "type": "DateTime2", "scale": 7 } |