We have a report running off a RDS database where the timestamps are in UTC but the data type is “TIMESTAMP WITHOUT TIMEZONE”. When we try and apply Quicksight automatic time zone adjustment, the adjustment is in the wrong “direction”. I.e. given the below times in UTC:
We would expect that upon changing the timezone to “Paris” that in the above report “9:16:38” would be adjusted to “11:16:38”, instead, as shown below, the time is adjusted backwards and becomes “7:16:38”.
This behaviour is consistent for all timezones. Is this a Quicksight issue or an issue with our timestamps being “without timezone” within Postgres?
1 Like
Hello @Cian_Mc_Sweeney, my initial thought would be to utilize a conversion calculation in the SQL for the field on ingestion rather than running it through the QuickSight time zone adjustment. I’m not certain what would cause that error so I am curious if managing it in the SQL query would resolve it.
I can link a stackoverflow article I found as well that explains how you would write that for RDS Postgres. Let me know if this helps!
Hello @Cian_Mc_Sweeney, since we have not heard back from you, I wanted to check in and see if my above response helped guide you towards your expected output. Please let me know if you have any remaining questions or mark my reply as the solution if it worked. Otherwise, if we do not hear back from you in 3 days, I will archive this topic. Thank you!
Hello @Cian_Mc_Sweeney, since we have not received any follow-up information from you, I will archive this topic. If you still need assistance with this, please post a new question in the community. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. Thank you!