Data 360: Issue with CSV Time format ingestion

If your input CSV file includes date-time fields in the following format:

2025-03-01T00:00:00.000-700
06-14-2022 00:00:00 UTC

Post ingestion into Data 360 (formerly Data Cloud), the date-time fields are either incorrectly parsed or show up as as incorrect time when viewed via the Data Explorer.
Through detailed review and testing, we've identified the following contributing factors:

Incorrect Timezone Format:

• • The value -700 or UTC is not a valid ISO 8601 timezone format.
  • ISO 8601 expects timezone offsets to be in the format -07:00 or UTC

Mismatch in Parsers:

• During ingestion, the CSV parser attempts a best match and incorrectly infers the format as: yyyy-MM-dd'T'HH:mm:ss.SSSSS
• However, Local File Upload uses a strict parser (DateTimeFormatter) which does not support lenient parsing like Spark or SimpleDateFormat. As a result, the invalid timestamp fails to parse and is treated as null.

Manual UI Format Correction Fails:

1. Manually setting the format in the UI to one of the following does not resolve the issue:

• yyyy-MM-dd'T'HH:mm:ss.SSSXXX
• yyyy-MM-dd'T'HH:mm:ss.SSSZZZ
• yyyy-MM-dd'T'HH:mm:ss.SSS ZZZ
• yyyy-MM-dd'T'HH:mm:ss.SSS Z