“Amazon Quicksight cant parse the data because it contains invalid dates or invalid numbers.Make sure your data contains only supported number and date formats”.
Why do I keep getting this error on my dashboard. The dataset is populating the data but i keep getting this error. In the quest to find the root cause for one particular case its being caused by a date field(with null values and date values) . While other date fields are populating but when I add this particular date field its showing the parsing error. And now its happening more often with few of my other dashboards. I checked all the formatting options and all but nothing seems to be out of order. Why am I getting this error. Could someone help me out to address this?
Hi @Nagamani and welcome to the QuickSight community!
I just recently encountered a similar issue in another community post where another user was encountering the same issue.
First thing to confirm would be if you’re utilizing one of the supported date formats within QuickSight. You can find those at the following link:
You mentioned that other date fields are populating? If that’s the case, is there anything in the structure of those fields that seems different from the date field that’s causing the error?
If you’re using a supported date format and the setup of the field is identical to another date field that’s working, this may be a bug within the system. And if so, I would suggest creating a support ticket so that you can get more direct support from the AWS team.
Hey Brett
Thank you for taking time to respond.Date format seems fine and the data also looks good (with all either null or a value). No unexpected entries in the database. Unable to understand the root of this error as offlate lot of my SPICE datasets are also throwing refresh failure errors due to the error caused by the date field ingestion errors. I am now confused why few date fields are showing up but few are throwing parsing errors although all are same date types.
Tried for creating a ticket but I dont think i know the right way to do it…some authentication error while singning to create a support ticket…Can anyone help me out here
Hi @Nagamani,
Did the error rows file provide any type of insight into the skipped rows? I’ve encountered scenarios where one field’s value may be incorrect and then all rows past that error do not return. So if you had an improper value in row 200, rows 201+ would not populate because of the error in row 200. So potentially you could try to check row 2591 under billing period date to see if that value is valid or not.
Normally only account admins are able to create support tickets, which may be why you’re running into an authentication issue; I would suggest double checking with your account admin to see if they can assist with the support ticket.
Hi @Nagamani
Since there is a link to download the errror rows file you could download that file. Can you share the date values for billing_period_date and start_date ?
Also you could try creating a dataset with just those two fields from the error file and see what happens.
Hi @Nagamani,
Following up here as it’s been awhile since we last heard from you; did you have any additional questions regarding your initial post or were you able to find a work around?
If we do not hear back within the next 3 business days, I’ll close out this topic.
Thank you
Hey all…Thank you for the response to address my issue. In regards to my issue…although the dataset was loading the data…the issue was with visualization which was giving parsing errors. On deep dive, I encountered few dates which was causing that issues…Once I fixed those dates the parsing error was gone. For example, one of the date was 0219-mm-dd , instead of the year 2019 , which was the cause of the error. So, on looking further, we found around 80 such corrupt dates(especially years) which were the cause of the error (probably human errors at data entrt points). So, Yaaa the data fix with respect to those years solved the issue for NOW. Once again Thank you all for trying to help me with my issue…Appreciate the community and the efforts to help out .
1 Like