ElegantInsights
AI settingsTimezone

Timezone

Auto-detected for accurate date filtering.

Last updated on

Default: Not set · Type: Text

Your timezone (a Windows timezone ID such as Pacific Standard Time), auto-detected from your browser on first visit. The assistant uses it to make date filtering in generated SQL accurate to your local time rather than UTC.

What changes

A non-UTC timezone changes the SQL itself: the assistant adds an AT TIME ZONE conversion so dates read in your local time (see the extra [Date Opened (Local)] column). UTC customers (the default) get raw datetimes, so it usually looks like the right-hand version.

Timezone set (e.g. Central Standard Time)

sql
SELECT    f.FaultID AS [Ticket ID],    f.Symptom AS [Subject],    a.aareadesc AS [Customer],    ts.TStatusDesc AS [Status],    f.DateOccured AS [Date Opened],    CAST(f.DateOccured AT TIME ZONE 'UTC' AT TIME ZONE 'Central Standard Time' AS DATE) AS [Date Opened (Local)]FROM Faults fJOIN Area a ON a.AArea = f.AreaIntJOIN TStatus ts ON ts.TStatus = f.StatusWHERE f.FDeleted = 0    AND f.Status <> 9    AND f.DateOccured >= @startdate    AND f.DateOccured < @enddate

UTC (default)

sql
SELECT    f.FaultID AS [Ticket ID],    f.Symptom AS [Subject],    a.aareadesc AS [Customer],    ts.TStatusDesc AS [Status],    f.DateOccured AS [Date Opened]FROM Faults fJOIN Area a ON a.AArea = f.AreaIntJOIN TStatus ts ON ts.TStatus = f.StatusWHERE f.FDeleted = 0    AND f.Status <> 9    AND f.DateOccured >= @startdate    AND f.DateOccured < @enddate

Where to change it

Set this under Profile → Prompt settings in the app. See all AI settings.

Date Format

How AI writes dates in explanations.

The community repository

A shared library of community SQL reports you can browse, vote on, run against your own Halo data, and contribute to.

On this page

Where to change it