We have a hub-and-spoke architecture with a central hub where reporting runs. All data resides at each operating location, often in different time zones.
We are having challenges with building reports that display the correct time and date for the time zone where the production is taking place. Specifically, when we are in Designer to build and preview a report we see a different timestamp (offset by the time zone differential) than when the report runs as scheduled. This situation occurs even when we are running the Designer in the same time zone as the central server.
- Hub Ignition Gateway located in US Central Time Zone - this is where the report will run
- Spoke/Location Ignition Gateway located in US Eastern Time Zone - this is where the production data resides
- Ignition project on Hub is configured: Project Properties Time Zone Behavior: US/Eastern
- Running Report Designer in central time zone (same TZ as the Ignition Gateway) the report preview shows shows batch end time of 15:25. When the report is generated automatically and emailed the end time for the same batch shows 14:25
We can certainly trial-and-error and figure out how to make this work by setting a report parameter for the hour correction factor, but would like to hear if:
Is it a bug or feature that the Report Builder displays a different time in preview mode and when run as scheduled (as described in the Example above)?
Has anyone figured out a programmatic way to handle preparing a report when the data resides in a different time zone from the Ignition gateway?
Has anyone figured out a programmatic way to handle sending reports at a consistent time of day when we transition to/from daylight savings? Of course we happen to have gateways in areas that are exceptions with respect to daylight savings so the time difference changes depending on DST.
Thanks in advance!