I do have others where the same date format is validated initially (ie the conversion modal shows samples of the data), but the conversion fails overall. This date format is standard for our RDS and I’ve done this conversion many times in the past on other datasets. Any ideas to investigate would be helpful!
Hi @kobrien and welcome to the QuickSight community!
My initial thoughts are that the error may be coming from the ‘.0’ added at the end of your format. I’ve attached a copy of the supported date formats below for review.
Something else you could consider if you are having issues; use parseDateto create a date field in your dataset and then use that date field to change formatting.
I did try parsedate as a workaround - it caused dataset refresh errors unfortunately. I may do this at the dataset level, however, to see how it behaves and avoid the refresh error.
One interesting realization I had - I was able to update the date format in the original dataset with only a single datasource using the format yyyy-MM-dd HH:mm:ss.SSS. This did not work in my current dataset where I have joined several datasources. Here is my dataset for reference, with the dataset in red causing the error -
parsdate() on the analysis-level works as a workaround! The issue remains of not being able to convert a string to a date in a datasource that is joined to others, but the workaround is good enough for my purposes. Thanks for your engagement, @Brett !
