Defining connection timezone settings
Connections have a few settings that allow you to specify how time-based data is converted:Defines the timezone the database is in. The specified timezone is used as the source timezone for any timezone conversions.
Defines the timezone to convert data to when querying.
- If Do Not Convert is selected, the Query Timezone will be UTC and no conversion will occur.
- If a timezone is selected:
- When querying, data will be converted from the Database timezone to the selected timezone
- In Omni, fields with timezone data will display in the Query Timezone. This also applies to filters with references to relative times and dates, such as today, yesterday, and so on.
- And the connection is to Snowflake, if you specify any
timestamp_tzfields will be displayed in that timezone. Otherwise, they will keep their timezone offset as-is.
If enabled, individual users’ Query Timezone setting will be used as the query timezone for the connection.
Determining the converting timezone
Omni determines the converting timezone using the following priority order:- Per-page timezone override (if enabled) — Set via the timezone picker on dashboards and workbooks
- User profile timezone (if connection allows user-specific timezones) — Set in the user’s profile settings
- Connection query timezone — Set in the connection settings
- Connection system timezone — Defaults to UTC
Preventing timezone conversion
To prevent timezone conversion for a field, add theconvert_tz: false property to the field in model. Note: This applies only to fields that don’t contain timezone information.
