You are here:
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
| Available in Salesforce Classic and Lightning Experience. |
| Available for an extra cost in Enterprise, Performance, and Unlimited Editions. Also available in: Developer Edition |
This table summarizes what happens when you enable time zone support, the actions you must take to update assets or stop using the feature.
| Feature | Time Zone Support Off | Time Zone Support Enabled | Actions to Upgrade Assets | Front-End Revert |
|---|---|---|---|---|
| Data Sync | Salesforce Date and Date Time fields generated as type Date | Existing connected objects continue to work. When data sync runs, Salesforce Date and Date Time fields are auto mapped to type DateOnly or DateTime. Input date values assumed to be GMT. |
Run data sync to update connected Salesforce objects. | No changes. Time zone fields are still generated. |
| Remote Connections | All date fields generated as type Date. | When sync runs, Date fields auto mapped to type DateOnly or DateTime. Input date values assumed to be GMT. | Run data sync to update connected external objects. | No changes. Time zone fields are still generated. |
| Data Prep Recipes and User Dataflows | Salesforce Date and Date Time fields generated as type Date | Existing dataflows and Data Prep Recipes continue to work, and generate time zone enabled datasets. Data Sync on: Date fields inherit type DateTime or DateOnly from connected objects. Data Sync off: Salesforce Date and Date Time fields auto mapped to type DateOnly or DateTime. Registered datasets with legacy Date type fields fetched in “edgemart” nodes are converted to datasets with DateTime type at runtime. |
Run dataflows and Data Prep Recipes to update datasets. Warnings prompt optional action. Some nodes have new parameter dateSyntax, which determines what syntax is used in their SAQL expressions. |
No changes. Time zone fields are still generated. |
| File Uploads | All date fields generated as type Date. | Automated uploads continue to work, and generate time zone enabled datasets. UI uploads generate time zone enabled datasets. Date field type auto detected and mapped to type DateOnly or DateTime. If auto detect not possible, Date field type mapped to DateTime. Input date values assumed to be GMT. In UI uploads, user can change auto-detected date field types and source timezone (if not GMT). |
No required action. Warnings prompt optional action. | No changes. Time zone fields are still generated. |
| Dashboards | All date fields generated as type Date. | Existing dashboards continue to work and are backwards-compatible with time zone enabled datasets. | Users can choose to build new time zone enabled dashboards, which use the Default Dashboard Timezone set in CRM Analytics settings. New SAQL syntax must be used with time zone enabled Dashboards. If a step references a non-time zone enabled dataset, it fails at runtime, but the rest of the dashboard loads. 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. |
Users must revert dashboards to use previous syntax and delete time zone enabled dashboards. Time zone enabled dashboards continue to work. No option to create time zone enabled dashboard or lenses from the Spring ’18 release. |
