Currently, relative date time is in UTC by default. So if I have a filter that uses relative time, like ‘previous day’, data that spans across the whole day will not work for data that’s in my time zone.
I can see that in early 2024, the ‘custom time zone’ feature was added to Quick.
But if I use a custom time zone, this will apply across all filters and also automatically convert time - the opposite of what I want!
My data in the dataset is already in my local time, not UTC, and ingested as SPICE.
Can we please have the option to convert Quick filters to local timezone, but not touch the data in the analysis?
Hi @dsbundle
I think your understanding about how QuickSight stores data in SPICE dataset is wrong. The data stored in QuickSight SPICE dataset is considered as UTC. The Custom Time-zone converts the datetime from this base to your desired timezone.
Just to show an example
I created a sample dataset with time in Europe/London time
With no timezone conversion the datetime shows what was present in my dataset
But if I change it to Europe/London it shows 10 pm. So it converted the dataset data assuming it to be UTC.
You may need to convert your datetime fields to UTC during ingestion to Quick Sight and then apply the time zone conversion to get the desired effect?
Regards,
Giri
Hi @dsbundle,
Just checking back in since this thread hasn’t received a response in a while. Was Giri’s reply helpful to you and/or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Thanks!
Hi @dsbundle,
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.
Thank you!
