Timestream data visualised incorrectly on Quicksight

[venieran]

I have connected a timestream table as a dataset (Direct Query). There, the “time” field is stored in UTC. However, we would like to use the Europe/Berlin time zone in our dashboard/analysis. However, according to this post, Timestream doesn’t support custom time zones. I then installed a calculated field “time-eu-berlin”. This field is correctly displayed in the dataset overview. parseDate (formatDate ({time}, "yyyy-mm-dd HH:mm:ss”, ‘Europe/Berlin’), “yyyy-mm-dd HH:mm:ss”) (see first screenshot)*
It is displayed incorrectly again on the dashboard. Interestingly enough, when I load some data into SPICE, it works.

Do you have any idea why this caused or how to solve this problem without using SPICE?

[duncan]

Hello @venieran , welcome to the Quick Sight community!

It might be helpful to try the calculated fields that are described in this blog:

Time Zone Adjustments

Most databases (including SPICE) store timestamps in UTC time. If you want to be able to dynamically adjust the time zone of the data displayed in your visuals for different users, we can do this using parameters and calculated fields. This technique will work both for if you want to allow Readers to change the time zone themselves (using a Control), or if you want to specify the time zone programmatically via the URL or via the JS SDK (for instance if you are embedding a dashboard in your appli…

This was created before custom time zones were available in Quick Sight.

Let me know if this helps/works