Using filters or parameters, users can narrow down which objects are displayed in a report based on data from Date & Time fields. However, this filtered data may be converted into the current user's time zone, depending on the field's configuration:
- If the Date & Time field is date-only (e.g., May 15, 2021), no conversion is applied.
- If the Date & Time field is date-time (e.g., 18:00 May 15, 2021), the data is converted based on the current user's local time zone.
This means that while some users in the same org but different time zones may not see the same report data, the data is provided in the user's local context. See the example below for more information.
Two users, one from London, England, and one from Melbourne, Australia, are accessing a report that contains four objects with both date-time and date-only data. The table below includes those objects along with the date-time equivalents for both regions.
|OBJECT||DATE & TIME|
|DATE & TIME|
|O-1||12:00 Dec 31, 2020||23:00 Dec 31, 2020||Dec 31, 2020|
|O-2||18:00 Dec 31, 2020||05:00 Jan 1, 2021||Dec 31, 2020|
|O-3||01:00 Jan 1, 2021||12:00 Jan 1, 2021||Jan 1, 2021|
|O-4||06:00 Jan 1, 2021||17:00 Jan 1, 2021||Jan 1, 2021|
If the user in London applies a report filter on the date-time field for January 1, 2021, they would see 2 objects on the report:
If the user in Melbourne applies a filter on the date-time field for January 1, 2021, they would see 3 objects on the report:
But if both the London and Melbourne users applied filters on the date-only field for January 1, 2021, they would see the same objects on the report: