Issue Summary
When using a SQL Connector to retrieve data containing datetimeoffset values stored in UTC, the timestamp conversion behavior within Tulip appears inconsistent with the Workspace Current Time Zone setting.
Observed Behavior
The SQL query returns datetime values correctly stored in UTC on the database server. However, when the data is received by the Tulip application, the timestamps are converted using the workspace’s Default Time Zone rather than the configured Current Time Zone.
For example, if the Workspace Current Time Zone differs from the Workspace Default Time Zone, the application displays timestamps adjusted to the Default Time Zone. After updating the Workspace Default Time Zone to match the intended Current Time Zone, the timestamps are displayed as expected.
Expected Behavior
Datetime values returned from the SQL Connector should be translated using the Workspace Current Time Zone setting, or the documented behavior should clearly indicate which workspace time zone setting governs connector datetime conversions.
Question
Can you confirm whether using the Workspace Default Time Zone for SQL Connector datetime conversions is the intended behavior, or if this is a defect in how datetimeoffset values are processed and displayed within Tulip applications? I dont know if this is specific to the SQL connector environment but this is where I found it.
Thank you