Documentation

BigQuery import fails due to timestamp mapping errors (CONNECTOR‑2001‑500 | MAPPER-3700-199)

Last update: Fri Feb 06 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Importing a BigQuery table into Adobe Experience Platform (AEP) through the native connector fails due to timestamp field mapping errors. The same dataset ingests successfully through CSV or FTP, which isolates the issue to timestamp handling in the BigQuery dataflow. To resolve the issue, align timestamp formats with schema mappings.

Description description

Environment

  • Product: Adobe Experience Platform (AEP)
  • Scenario: BigQuery native source connector ingestion

Issue/Symptoms

  • Import of a BigQuery table using the native connector fails during ingestion.
  • The process returns the error CONNECTOR-2001-500 (Error in processing/parsing/validation/transformation).
  • Diagnostics report timestamp field transformation warnings with the error “code”: “MAPPER-3700-199”, “description”: “Field transformation warning” and details stating Error invoking date(java.lang.String,java.lang.String) caused by : Unable to parse date  22:30:00 EST with format yyyy-MM-dd HHss zzz.
  • Importing identical data through CSV or FTP completes successfully without errors.

Resolution resolution

Follow these steps to address the issue:

  1. Verify whether the timestamp field is marked as Required in the Adobe Experience Platform schema. If this requirement is not necessary, uncheck the Required option.
  2. Confirm that the source BigQuery table contains a timestamp column and that the column is correctly mapped in Data Prep.
  3. Check the source data for null or empty values in the timestamp column. Correct the data or remove affected rows.
  4. Ensure all timestamp values follow RFC 3339 or ISO 8601 formats (for example, 2024-01-15T10:00:00Z).
  5. Reimport the corrected batch using the BigQuery connector.
  6. Verify that the import completes successfully and that no timestamp-related errors are reported.

Note: If the issue persists, review the transformation logic and examine any additional error messages for further details.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f