--- schema_version: "1" id: a32ab66a9fcd22fcccf6cbd6300d91566b068452a150051d1ca6940bdbc0ba91 title: Custom Time Zone Considerations 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_limitations.md canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_setup_time_zone_support_limitations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 1aee22f5c3134a63274ee6f06f934f464da270483062c62ece3fb5a1e46472da description: Keep these considerations in mind when working with custom time zones. products: - CRM Analytics - Cross Cloud release: "264" --- # Custom Time Zone Considerations Keep these considerations in mind when working with custom time zones. ### 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
Create Data Source Links in a Time Zone Enabled Dashboard You can create data source links using date fields (DateOnly and DateTime) in time zone enabled datasets. If two datasets are linked using the parent date field (such as CreateDate), all components of the date field (such as year and year-month) are automatically linked. Data source links between a static step and an individual date component of a DateOnly or DateTime field aren’t supported. Bind Dates in a Time Zone Enabled Dashboard When binding dates in a time zone enabled dashboard, you refer to date fields differently. Note the following differences between GMT-only dashboards and time zone enabled dashboards. | GMT-Only Dashboards | Time Zone Enabled Dashboards | | --- | --- | | `cell(myStep.selection, 0, "CloseDate_year")` | `cell(myStep.selection, 0, "year_CloseDate")` | | `cell(myStep.selection, 0, "CloseDate_year~~~CloseDate_month")` | `cell(myStep.selection, 0, "year-month_CloseDate")` | | `asEquality("CreateDate_year", "Region")` | `asEquality(["year", "CreateDate"], "Region")` | | `asDateRange("CreateDate('year', 'month', 'day')")` | `asDateRange("CreateDate")` | Use Compact Form Queries in a Time Zone Enabled Dashboard When adding dates in compact form queries, the syntax is different in time zone supported dashboards. Note the following differences between GMT-only dashboards and time zone supported dashboards.
Query Component GMT-only Dashboards Time Zone Supported Dashboards
Date Measure 
"measures": [
    ["sum", "Ship_Date_day_epoch"]
]
 
"measures": [
    ["sum", ["epochDay","Ship_Date"]]
]
Group by Date 
"groups": [
    "CloseDate_Year"
]
 
"groups": [
    ["year", "CloseDate"]
]
Group by Date 
"groups": [
    [
        "CloseDate_Year",         
        "CloseDate_Quarter"
    ]
]
 
"groups": [
    ["year-quarter", "CloseDate"]
]
Filter by Date 
"filters": [
  [
     "Created Date",
     [
         [
            1359504000000,
            1486425600000
         ]
     ],
     ">=<="
  ]
]
 
"filters": [
  [
    "Created Date",
    [
       [
          "2013-01-30 00:00:00",
          "2017-02-02 23:59:59"
       ]
    ],
    ">=<="
  ]
]
Filter by Date 
"filters": [
  [
    "Opportunity.CloseDate",
      [
        [
          [
            "quarter",
            -2
          ],
          [
            "quarter",
            0
          ]
        ]
      ],
      ">=<="
  ]
]
Unchanged
Order by Date 
"Order": [
 [
  "CreateDate_year", 
  {
   "ascending": true
  }
 ]
]

"order": [
  [
   ["year", "CreateDate"],
   {
    "ascending": true
   }
  ]
]
Other Considerations You can’t view converted date-time values in a lens. Time zone enabled dashboards don’t support these features: - Notifications - Subscriptions - Watchlists - Natural language queries - Data source connections between a static step and a dataset date field - Displaying month names, such as “Jan” and “Feb” (months display as numbers only, such as “01” and “02”) - Remote text-based search on date fields in list widgets