Hi @RoyceGoodwin Welcome to the QuickSight community 
If you’re referring to the error in the first screenshot, the field Resolutioncodevalue doesn’t look like to be a date. Is that the field you have updated the correct date format with in the next 2 screenshots you shared?
Would help if you provide more details please.
1 Like
The Resolutioncode is not a date, however The count of resolutioncodes has nothing to do with dates. No visuals are working because when changing the date format, for some reason it is making an error with all the data being uploaded.
Thats a little strange @RoyceGoodwin … I see you’re potentially using a csv file as your data source. If you make no changes to any of the date columns, are your visuals working fine?
1 Like
The visuals work fine, yes. But I can’t set up filter for dates because theya re still strings. So if I don’t change the format I can make visuals, without any relative dates to analyze, if I do make the format changes, I can’t make any visuals because it says the date format isn’t correct which the weirdest part is it actually accepts the date format. It is a little strange, I agree.
@RoyceGoodwin I am assuming you may have already tried creating a new dataset to see if that resolves the date issue? If you can share a file with few rows of dummy data, I am happy to check at my end too…
However, the fastest way for you to be able to resolve this would be filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!
1 Like