---
schema_version: "1"
id: ce44479b885ad0570c6e6da0bf8bb0aa3563cd9f733cc7662486ee434c9e3538
title: What Happens When You Enable Time Zone Support
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_setup_time_zone_support_what_happens.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_setup_time_zone_support_what_happens.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 11aab3560ee737089833951f35e8e13fd440c250c9c63dcb40f6270dc7b58df3
description: This table summarizes what happens when you enable time zone support, the actions you must take to update assets or stop using the feature.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# What Happens When You Enable Time Zone Support

This table summarizes what happens when you enable time zone support, the actions you must take to update assets or stop using the feature.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in Salesforce Classic and Lightning Experience.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available for an extra cost in <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions. Also available in: <a href="https://help.salesforce.com/articleView?id=bi_tutorials.htm&amp;language=en_US" target="_blank"><strong>Developer</strong> Edition</a></td></tr></tbody></table>

This table summarizes what happens when you enable time zone support, the actions you must take to update assets or stop using the feature.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:17.301038062283737%">
          <col style="width:17.301038062283737%">
          <col style="width:17.301038062283737%">
          <col style="width:17.301038062283737%">
          <col style="width:30.79584775086505%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d151993e72">Feature</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d151993e74">Time Zone Support Off</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d151993e76">Time Zone Support Enabled</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d151993e78">Actions to Upgrade Assets</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d151993e80">Front-End Revert</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e72 ">Data Sync</td>
            <td data-label="Time Zone Support Off" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e74 ">Salesforce Date and Date Time fields generated as type <strong>Date</strong></td>
            <td data-label="Time Zone Support Enabled" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e76 ">
              <p>Existing connected objects continue to work.</p>
              <p style="margin-bottom:0;">When data sync runs, Salesforce
                Date and Date Time fields are auto mapped to type <strong>DateOnly</strong> or
                <strong>DateTime</strong>.
              </p>
              <p style="margin-bottom:0;">Input date values assumed to be GMT. </p>
            </td>
            <td data-label="Actions to Upgrade Assets" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e78 "> Run data sync to update connected Salesforce objects. </td>
            <td data-label="Front-End Revert" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e80 ">No changes. Time zone fields are still generated.</td>
          </tr>
          <tr class="">
            <td data-label="Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e72 ">Remote Connections</td>
            <td data-label="Time Zone Support Off" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e74 ">All date fields generated as type <strong>Date</strong>. </td>
            <td data-label="Time Zone Support Enabled" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e76 ">When sync runs, <strong>Date</strong> fields auto mapped to type <strong>DateOnly</strong> or
              <strong>DateTime</strong>. Input date values assumed to be GMT.
            </td>
            <td data-label="Actions to Upgrade Assets" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e78 "> Run data sync to update connected external objects. </td>
            <td data-label="Front-End Revert" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e80 ">No changes. Time zone fields are still generated.</td>
          </tr>
          <tr class="">
            <td data-label="Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e72 ">Data Prep Recipes and User Dataflows</td>
            <td data-label="Time Zone Support Off" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e74 ">Salesforce Date and Date Time fields generated as type <strong>Date</strong></td>
            <td data-label="Time Zone Support Enabled" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e76 ">
              <p>Existing dataflows and Data Prep Recipes continue to work, and generate time
                zone enabled datasets.</p>
              <p>Data Sync on: Date fields inherit type <strong>DateTime</strong>
                or <strong>DateOnly</strong> from connected objects. </p>
              <p>Data Sync off: Salesforce Date and
                Date Time fields auto mapped to type <strong>DateOnly</strong> or
                <strong>DateTime</strong>.
              </p>
              <p style="margin-bottom:0;">Registered datasets with legacy <strong>Date</strong> type fields fetched
                in “edgemart” nodes are converted to datasets with <strong>DateTime</strong> type at
                runtime.</p>
            </td>
            <td data-label="Actions to Upgrade Assets" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e78 ">
              <p>Run dataflows and Data Prep Recipes to update datasets.</p>
              <p>Warnings
                prompt optional action. </p>
              <p style="margin-bottom:0;">Some nodes have new parameter <strong>dateSyntax</strong>, which
                determines what syntax is used in their SAQL expressions.</p>
            </td>
            <td data-label="Front-End Revert" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e80 ">No changes. Time zone fields are still generated.</td>
          </tr>
          <tr class="">
            <td data-label="Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e72 ">File Uploads</td>
            <td data-label="Time Zone Support Off" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e74 ">All date fields generated as type <strong>Date</strong>. </td>
            <td data-label="Time Zone Support Enabled" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e76 ">
              <p>Automated uploads continue to work, and generate time zone enabled datasets.
              </p>
              <p>UI uploads generate time zone enabled datasets. </p>
              <p><strong>Date</strong> field
                type auto detected and mapped to type <strong>DateOnly</strong> or <strong>DateTime</strong>.</p>
              <p>If
                auto detect not possible, <strong>Date</strong> field type mapped to <strong>DateTime</strong>.
              </p>
              <p style="margin-bottom:0;">Input date values assumed to be GMT. </p>
              <p style="margin-bottom:0;">In UI uploads, user can change
                auto-detected date field types and source timezone (if not GMT). </p>
            </td>
            <td data-label="Actions to Upgrade Assets" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e78 ">No required action. Warnings prompt optional action. </td>
            <td data-label="Front-End Revert" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e80 ">No changes. Time zone fields are still generated.</td>
          </tr>
          <tr class="">
            <td data-label="Feature" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e72 ">Dashboards</td>
            <td data-label="Time Zone Support Off" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e74 ">All date fields generated as type <strong>Date</strong>. </td>
            <td data-label="Time Zone Support Enabled" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e76 ">Existing dashboards continue to work and are backwards-compatible with time
              zone enabled datasets.</td>
            <td data-label="Actions to Upgrade Assets" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e78 ">
              <p>Users can choose to build new time zone enabled dashboards, which use the
                Default Dashboard Timezone set in CRM Analytics settings. </p>
              <p>New SAQL syntax must
                be used with time zone enabled Dashboards. </p>
              <p>If a step references a non-time zone
                enabled dataset, it fails at runtime, but the rest of the dashboard loads.
              </p>
              <p style="margin-bottom:0;">Date field formats are standardized, rather than displaying the date as
                ingested. The date format can be changed by converting the date to a string in the
                SAQL expression or by adding a string field of the full date to the
                dataset.</p>
            </td>
            <td data-label="Front-End Revert" class="slds-cell-wrap" style="vertical-align:top;" headers="d151993e80 ">
              <p>Users must revert dashboards to use previous syntax and delete time zone
                enabled dashboards. </p>
              <p style="margin-bottom:0;">Time zone enabled dashboards continue to work. </p>
              <p style="margin-bottom:0;">No option
                to create time zone enabled dashboard or lenses from the Spring ’18 release.
              </p>
            </td>
          </tr>
        </tbody>
      </table>