Date Format Validation Issue in New DataPrep - ISO 8601 Format Not Working

Q&A
, , ,
1

We are experiencing a critical issue with date field formatting in the new QuickSight DataPrep interface that is preventing us from migrating from the legacy DataPrep view.

Background: All of our date fields are formatted as ISO 8601 datetime strings (e.g., 2024-07-01T06:00:00.000Z). We have been successfully using this format within QuickSight for years without issue.

Issue Details:

  1. Legacy DataPrep (Working): In the old DataPrep view, our date format is correctly read and validated using the format string: yyyy-MM-dd'T'HH:mm:ss.SSSZZ (see Image 1)

  2. New DataPreep (Not Working): Using the identical data and the same date format string yyyy-MM-dd'T'HH:mm:ss.SSSZZ in the change data type prep step (see Image 2):

    • The “Validate” button does not appear to attempt formatting the result

    • We cannot successfully apply the format (see Image 3)

  3. Alternative Formats Fail: When attempting to use one of the suggested supported formats from the dropdown, we receive an error stating that the data does not comply with the format (see Image 4)

Business Impact: This issue leaves us in a difficult position where we can only use the legacy DataPrep view. Migrating to the new DataPrep interface would require reformatting every date field sent to our datasource—a significant undertaking that would impact multiple data pipelines and systems.

Expected Behavior: The new DataPrep should support the same date format string (yyyy-MM-dd'T'HH:mm:ss.SSSZZ) that works in the legacy DataPrep view, allowing us to validate and apply date formatting to ISO 8601 datetime strings.

Request: Please investigate why the date format validation is not working in the new DataPrep interface and provide guidance on how we can process ISO 8601 formatted dates without requiring extensive changes to our data sources.

FYI It would be great if I could upload more than 1 image in this request.

Screenshot 2025-11-05 at 5.59.02 PM
Screenshot 2025-11-05 at 5.59.02 PM621Ă—816 51.3 KB

2

Hi @ericsloan and welcome to the Quick Suite Community!
Thank you for the detailed information and bringing this to attention! As you’ve noticed, there are still some limitations within the new Data Prep experience, which is why the legacy version is still available for use in these scenarios. I’ll include a link below that details the current limitations for the new data prep feature. To my understanding though, the legacy version will continue to be available until these features are also brought in to the new experience so you’ll have that availability.
Additionally, I’ll mark this as a feature request so that the support team can review as they work through additional implementation steps for the new data prep!

3

@vignessh.b, adding you here for visibility!

4

@ericsloan (cc: @Brett ) Thank you for flagging this. We’re looking into the support of this date format. Will respond once we have an update.

1 Like