DemandFlow Support Centre

TIMEZONE: Timezone

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A timezone reference record with UTC offset, abbreviation, and daylight savings flag for time coordination.

TIMEZONE: Timezone

A timezone reference record with UTC offset, abbreviation, and daylight savings flag for time coordination.

Default definition. This article describes the default TIMEZONE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches TIMEZONE.

Entity properties

PropertyValue
Entity codeTIMEZONE
Display nameTimezone
PluralTimezones
Level250

Use cases

A timezone reference record with UTC offset, abbreviation, and daylight savings flag for time coordination.

TIMEZONE is a reference data entity for managing timezone information across the platform. It uses the simple grid view. The name field stores the full timezone identifier (e.g., 'Eastern Standard Time'), abreviation stores the short form (e.g., 'EST' - note the field name has a spelling variation from 'abbreviation'). The utcOffset is a numeric field storing the hours offset from UTC (e.g., -5 for EST, +1 for CET), with sort enabled to allow ordering timezones by offset. The dst checkbox indicates whether the timezone observes daylight saving time, which is important for scheduling across time boundaries. The comments textarea allows notes about timezone edge cases or regional variations. Timezone records support distributed team coordination, meeting scheduling, and deadline management where participants span multiple time zones. At level 250, it sits alongside other reference data in the admin area.

Fields

General

FieldTypeRequiredNotes
nametextYesName.
abreviationtextYesAbreviation.
utcOffsetnumberYesUTCC offset.
dstbooleanYesUses daylight savings.
commentstext (multi-line)Comments.

Relationships

No declared relationships in the default definition.

Creating a Timezone via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "TIMEZONE",
  "level":    250,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "abreviation": "Example abreviation",
  "utcOffset": 0,
  "dst": true
}

Listing Timezones

GET /v1/entities/TIMEZONE/SUB

See also

timezonetimezones

Was this article helpful?

← Back to Knowledge Base