# Date string and parsedate problem **URL:** \ **Category:** Q&A\ **Tags:** quick-sight\ **Created:** [June 4, 2023, 4:43am UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229 "2023-06-04T04:43:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![waisal01](https://avatars.discourse-cdn.com/v4/letter/w/a3d4f5/32.png) [@waisal01](https://community.amazonquick.com/u/waisal01)\ **Post date:** [June 4, 2023, 4:43am UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/1 "2023-06-04T04:43:40Z")
My dataset has this [verified date] field, initial data type = integer, I convert it to date type, it fails to populate at quicksight, ![data-date](https://d1wl4jav5dp96l.cloudfront.net/original/2X/c/c3bb82a1d8e13b3df5025b0a4e3f932b1a9a4bbf.png) Seeking community member advice on this matter… ---
**Author:** ![waisal01](https://avatars.discourse-cdn.com/v4/letter/w/a3d4f5/32.png) [@waisal01](https://community.amazonquick.com/u/waisal01)\ **Post date:** [June 4, 2023, 4:52am UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/2 "2023-06-04T04:52:43Z")
Then i convert it to string type, followed by parsedate function, it fail to populate too. Tried ifelse+parsedate function as proposed by another member, still fail to populate the data… ![data-string](https://d1wl4jav5dp96l.cloudfront.net/original/2X/4/4a74d5f8e51450d603d20564e5688f41d60a7f9c.png) Seeking community member kind advice on this matter… ---
**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:** [June 4, 2023, 7:34am UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/3 "2023-06-04T07:34:59Z")
Hi @waisal01 - Welcome to AWS Quick Sight community and thanks for posting the question. Can you please change the data type in dataset preparation page, by selecting the column and change the type to date and give the format. Validate the data in data set page and then used for your analysis. ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/e/e910d7b84261b18f79bb774b05360812fcb9863b.png) Regards - Sanjeeb ---
**Author:** ![waisal01](https://avatars.discourse-cdn.com/v4/letter/w/a3d4f5/32.png) [@waisal01](https://community.amazonquick.com/u/waisal01)\ **Post date:** [June 4, 2023, 12:49pm UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/4 "2023-06-04T12:49:15Z")
Hi! Sanjeeb, Tried as per you suggestion format MM-DD-YYYY. Same problem & SQL error message. ![data-date-retry](https://d1wl4jav5dp96l.cloudfront.net/original/2X/4/4f26680521d8b34e4c700dcc60d0542ebc2d9f45.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:** [June 5, 2023, 8:05am UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/5 "2023-06-05T08:05:08Z")
Hi @waisal01 - It looks like all the records are not in the same format. Can you please raise a ticket to AWS Customer support team to help you on this and provide the request ID from your screenshot. To raise a request, please follow the link - [Creating support cases and case management - AWS Support](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html). Regards - Sanjeeb ---
**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\ **Post date:** [June 7, 2023, 12:56pm UTC](https://community.amazonquick.com/t/date-string-and-parsedate-problem/14229/6 "2023-06-07T12:56:27Z")