Reports, Time zone, report viewer
Summary
The date and time printed on Cloud 9 reports is the server's time (Eastern), not the time zone of the office running the report. This is expected behavior today, not a data or configuration error.
Practices in other time zones, such as Central, Mountain, and Pacific may see a printed run time one/two/three hour ahead of their computer clock.
Why this happens
The printed date and time on a report has no concept of time zone. It cannot read the user's browser or office time zone, so it falls back to the local time of the server that generates the report.
The Cloud 9 server runs on Eastern time (EST). "Local" in this case means local to the server, not local to the user.
Example
A Central-time office ran the Daily Collections report in the Report Viewer. The report header printed a different time than the computer clock.
| Source | Time shown |
|---|---|
| Computer clock (Central) | 11:25 AM |
| Printed date/time on report (server, Eastern) | 12:25 PM |
A one-hour gap between the computer clock and the printed report time, with the report ahead, is the expected result for offices outside of the Eastern time zone.
Impact and workaround
Only the printed date and time on the report is affected. The report data, such as collections for a given date, is not changed by the time zone.
There is no setting to change the printed time zone. When reviewing a printed report, treat the run time as Eastern and subtract the difference for your office's time zone (for example, one hour for Central).