# Field date values were not supported **URL:** \ **Category:** Q&A\ **Tags:** data-source, quick-sight\ **Created:** [August 16, 2023, 7:06am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051 "2023-08-16T07:06:29Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 16, 2023, 7:06am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/1 "2023-08-16T07:06:29Z")
Hi, anybody encountered this issue with MYSQL database date field format? Is there a specific fix as my refresh always failed. ---
**Author:** ![andres007](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/andres007/32/8734_2.png) [@andres007](https://community.amazonquick.com/u/andres007)\ **Post date:** [August 16, 2023, 7:30am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/2 "2023-08-16T07:30:40Z")
Hello @ebernardinojr, Can you give us a little more information about what version of DB are you trying? What is the field type on the source and what kind of error do you get when refreshing? If you can post the DDL of the field on the table you are trying to refresh I can try to replicate and see if I can help you further. Kind regards, Andres. ---
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 16, 2023, 7:46am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/3 "2023-08-16T07:46:58Z")
Hi Andres, Thank you for responding immediately Version MySQL 5.7.38, field type is DATE. It use to work until a row was inserted with possibly an invalid date format. Below is the specific error, the dataset is can no longer be refresh The SKIPPED ROWS 1 rows where BIRTHDATE field date values were not supported. ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/a/ad19fb935b768efb1c75a152e0a9b4e051cbfca2.png) ---
**Author:** ![andres007](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/andres007/32/8734_2.png) [@andres007](https://community.amazonquick.com/u/andres007)\ **Post date:** [August 16, 2023, 4:31pm UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/4 "2023-08-16T16:31:53Z")
Hi, Is it possible to fix the row with the incorrect date? Can you click the download error rows file to see what is the date that is failing? I find it strange that the value is accepted on the field by MySQL but it fails when importing into Quick Sight, let’s dig a little more deeper. Kind regards, Andres. ---
**Author:** ![Sanjeeb2022](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/sanjeeb2022/32/20947_2.png) [@Sanjeeb2022](https://community.amazonquick.com/u/Sanjeeb2022)\ **Post date:** [August 16, 2023, 5:17pm UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/5 "2023-08-16T17:17:22Z")
Hi @ebernardinojr - Give some sample rows so that right format can be set at data set level. Regards - Sanjeeb ---
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 17, 2023, 1:08am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/6 "2023-08-17T01:08:31Z")
sharing the specific error ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/9/937f462cfe360394bcda29b1f2f26bf6d9db0493.png) ---
**Author:** ![Sanjeeb2022](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/sanjeeb2022/32/20947_2.png) [@Sanjeeb2022](https://community.amazonquick.com/u/Sanjeeb2022)\ **Post date:** [August 17, 2023, 3:22am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/7 "2023-08-17T03:22:48Z")
Hi @ebernardinojr - If you see the BIRTHDATE, it is not a date field. Please fix your data first. If there is an issue with data, QS is not able to parse it, its good it is throwing the error. Regards - Sanjeeb ---
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 17, 2023, 3:36am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/8 "2023-08-17T03:36:14Z")
the front end accepted a date value, it might be an issue on the mysql version ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/d/d5f924b47e6f63301e2ff720dc9658033f2f0eee.png) ---
**Author:** ![Sanjeeb2022](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/sanjeeb2022/32/20947_2.png) [@Sanjeeb2022](https://community.amazonquick.com/u/Sanjeeb2022)\ **Post date:** [August 17, 2023, 4:33am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/9 "2023-08-17T04:33:50Z")
Hi @ebernardinojr - Is it possible to see this data from mysql? Clearly the data is not in the date format. You have to fix this data issue before importing to Quick Sight , if all fields are same format, you can use transform to a date format in Quick Sight as well. Regards - Sanjeeb ---
**Author:** ![andres007](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/andres007/32/8734_2.png) [@andres007](https://community.amazonquick.com/u/andres007)\ **Post date:** [August 17, 2023, 10:13am UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/10 "2023-08-17T10:13:56Z")
Hello, That looks like an EPOCH, but even if that is stored in miliseconds and a birthdate that looks like it is still a very very old person. Probably the frontend is not validating a “reasonable” age and allowed someone to enter an invalid age. I made some tests on my database and was able to reproduce the rows with “very old” dates to fail to be loaded into SPICE. Looking at the documentation > **[Supported date formats - Amazon QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/supported-date-formats.html)** > > Amazon QuickSight supports the date and time formats described in this section. Before you add data to Amazon QuickSight, check if your date format is compatible. If you need to use an unsupported format, see . > For datasets stored in memory (SPICE), Amazon Quick Sight supports dates in the following range: `Jan 1, 1400 00:00:00 UTC` through `Dec 31, 9999, 23:59:59 UTC` . Where the date that is failing for you falls outside the allowed range for SPICE. Hope this helps! Kind regards, Andres. ---
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 19, 2023, 12:58pm UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/11 "2023-08-19T12:58:41Z")
thanks, this is really helpful ---
**Author:** ![ebernardinojr](https://avatars.discourse-cdn.com/v4/letter/e/b77776/32.png) [@ebernardinojr](https://community.amazonquick.com/u/ebernardinojr)\ **Post date:** [August 19, 2023, 12:59pm UTC](https://community.amazonquick.com/t/field-date-values-were-not-supported/17051/12 "2023-08-19T12:59:21Z")
thanks, we adjusted the data directly