Loading

Warning "The extract has a different time zone from the underlying server"

Julkaisupäivä: Apr 24, 2025
Kuvaus
When creating an extract, you may encounter the following warning:

The extract has a different time zone from the underlying server. Calculations using TODAY() and NOW() and relative date filters will give different results. 

Cause

This message appears because the time zone of the data source does not match the time zone of the computer on which the extract was created.
Ratkaisu

To adjust date/time fields:

Use a calculated field to add or subtract hours from the current date field to reflect a specific time zone. For example:
DATEADD('hour', -7, [Date]) 

To filter to the most recent hour of the data:

  1. Create a calculation for computing whether [DateTimeField] is greater than or equal to the maximum date/time of the dataset: 
    [DateTimeField] >= {FIXED: MAX(DATETRUNC('hour', [DateTimeField]))} 
  2. Place the calculation on the Filter Shelf, choose to show "True" 


Filter to NOW() adjusted to timezone:

The below example adjusts from UTC (timezone of most Postgres databases) to Eastern Time Zone.  
  1. Create calculation for computing whether [DateTimeField] is equal to or greater than NOW() in Eastern Time: 
    [DateTimeField] >= DATEADD('hour', -5, NOW()) 
  2. Place the calculation on the Filter Shelf, choose to show "True" 

 

Lisäresurssit
  • The time zone difference impacts the relative date filters as well as the NOW() and TODAY() functions. 
  • Live connections use the time zone of the database whereas extracts use time zone of the local computer operating system.


Knowledge-artikkelin numero

001473632

 
Ladataan
Salesforce Help | Article