Hi Team,
Currently, OAC provides an option for users to view reports based on the timezone configured in their user profile. However, this timezone conversion is not applied when the same report is exported to Excel. In the exported file, the date and time are displayed in the source timezone instead of the user's configured timezone.
For businesses operating across multiple countries and timezones, this is an important and basic functionality. Users should be able to see consistent date and time information in both the OAC report and its exported files. This is particularly important for our customer, as OAC is used by users across multiple countries such as Germany, the UK, Australia, etc., and each user expects to see the data in their respective local timezone.
We request that this functionality be extended to exports such as Excel so that the timezone conversion applied in OAC is also reflected in the exported data. This would provide a consistent user experience and avoid confusion when users analyse or share exported reports.
Additionally, there is another issue with the current timezone conversion in OAC. The conversion does not appear to account for Daylight Saving Time (DST).
For example, if the Work Order Closed Date is stored in UTC in the database and is converted to Central European Time (CET), OAC currently adds 2 hours to the UTC time in all cases. However, the actual difference between UTC and Central European local time changes depending on whether DST is active. During the non-DST period, the difference is 1 hour, while during DST it is 2 hours.
Therefore, the conversion should dynamically consider the date and determine whether DST was applicable at that point in time, rather than applying a fixed offset.
In my view, resolving this DST issue should be considered a prerequisite before implementing the timezone conversion for exports. Otherwise, the exported data could still contain incorrect date/time values even if the user-level timezone conversion is extended to Excel.
Could you please consider addressing both of these points in upcoming OAC releases?
Thanks,
Darsh
