> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# convert_tz

> Controls whether a field should be converted to the query/user timezone.

When set to `false`, the field will default to the [connection (database) timezone](/connect-data/timezones) with no conversion.

This parameter can only be added to a dimension and will apply to all the parameterizations of the dimension. Date or week fields in the database are good candidates for this parameter, as converting the time segments isn't necessary.

<Note>
  Timezone conversion in a [`sql` parameter](/modeling/dimensions/parameters/sql) is strongly discouraged. This approach can create challenges on SQL generation for complex transformations, such as dimension fill vis-a-vis timezones.
</Note>

## Syntax

```yaml theme={null}
<dimension_name>:
  convert_tz: false
```

## Properties

<ParamField path="dimension_name" type="object">
  The name of the dimension. Dimension names must:

  * Be unique within the view
  * Start with a letter
  * Contain only alphanumeric characters and underscores

  <Expandable title="dimension_name properties" defaultOpen="true">
    <ParamField path="convert_tz" type="boolean" default="true">
      When set to `false`, timezone conversion will be disabled for the field, instead defaulting to the [database timezone](/connect-data/timezones) with no conversion. Defaults to `true`.
    </ParamField>
  </Expandable>
</ParamField>

## Examples

```yaml title="Disable timezone conversion" theme={null}
created_date:
  sql: created_date
  convert_tz: false
```

```yaml title="Date field with timeframes" theme={null}
timestamp_created_pst:
  sql: DATETIME(${marketing_orders_new.timestamp_created}, 'America/Los_Angeles')
  timeframes:
    - DATE
    - HOUR_OF_DAY
    - MONTH_NAME
  convert_tz: false
```