Spotfire Ideas Portal
Datasets from sources that use a timestamp with timezone field are read incorrectly in Spotfire. See:
https://support.tibco.com/s/article/Values-in-a-column-of-type-Timestamp-with-timezone-are-different-from-original-values-when-imported-through-Information-Designer
The consequence is that the reports can be incorrect and show different results in different locations
We're testing a recent Snowflake JDBC driver (3.25.1) with a view to deploying. Using the driver we have been using for the last few years (3.13.8), a Timestamp with timezone column (TIMESTAMP_TZ in Snowflake) kind of works in Spotfire in that Info Designer creates it as a DATETIME and info links pull it through as DATETIME.
But with the 3.25.1 driver, it blows up - it creates the column as a STRING and executing an Info Link causes an "unsupported type" error. The fix is to manually edit the Column to a DATETIME and to use a CAST expression to convert it to a DATETIME (converting to TIMESATAMP will also work).