- Does anyone know why importing historical ticket data from Zendesk into Genesys Cloud Reporting results in a 400 Bad Request error?
- We are trying to map Zendesk ticket fields to Genesys Interaction attributes for a unified view. The Zendesk CSV uses a simple timestamp format, but Genesys expects ISO 8601 with timezone offsets.
- The specific error message returned is: ‘Invalid value for field created_at: Expected format yyyy-MM-ddTHH:mm:ss.SSSZ’.
- We are using the Genesys Cloud Analytics API endpoint /api/v2/analytics/reporting/import to push the data. The SDK version is 1.0.5.
- In Zendesk, we could just dump raw CSVs into the export tool and it handled date parsing automatically. Genesys seems much stricter about schema validation during bulk imports.
- Has anyone successfully mapped Zendesk ticket timestamps to Genesys interaction start times without losing data fidelity?
- We are currently in the Europe/Paris timezone, which might be causing the offset calculation to fail if the system expects UTC by default.
- Any advice on preprocessing the CSV in Python or using a specific Architect flow to transform dates before the import would be appreciated.
- We want to avoid manual reformatting for thousands of historical tickets.