I have determined that Spice does not support milliseconds which in turn records are being aggregated due to having the same date/time. Is there a way to disable this so all records are shown?
The following example, though simplified and far less columns, demonstrates 2 records are aggregated due to having the same time. The underlying data has been also verified.
I would also been keen to understand how others have overcome the lack of support of milliseconds using Spice.
First of all Welcome to the QuickSight Community !
For datasets stored in memory (SPICE), Amazon QuickSight supports dates in the following range: Jan 1, 1400 00:00:00 UTC through Dec 31, 9999, 23:59:59 UTC.
How big is your data set ? is there a way to use direct query ? and if its relational db there may be possibility to include milliseconds. Please see the supported date format: Supported date formats - Amazon QuickSight
Thanks, I did go through the documentation highlighted after discovering this limitation with Spice. At present there is no option to alter this approach. The limitation has only become an issue due to data/time being aggregated as shown within my example, and even with milliseconds the same scenario could happen. Is there a way of disabling the aggregation to just present every row?
Hi @Jamie,
It’s been awhile since we last heard from you. Were you able to find a work around to your issue using abacon’s suggestion or are you still encountering issues?
If we do not hear back from you in the next 3 business days, I’ll go ahead and archive this topic. If you have any further questions past that, feel free to create a new topic for discussion and link this page for relevant information.
Hi @Jamie,
Since we haven’t heard back, I’ll go ahead and mark the solution. However, if you have any lingering questions, feel free to create a new topic in the community and link this discussion for relevant information.