Fire Journey Event REST Endpoint does not respect UTC time conversion when using 'Z' zone designator
Last updated 2020-04-17 ·Reference W-6337387 ·Reported By 1 users
When using the REST endpoint to fire a journey (/interaction/v1/events), if a data extension date field is included with an ISO 860 standard UTC value using the 'Z' zone designator for zero UTC offset, then there is no conversion to server time.
-Create a Data Extension with fields SubscriberKey, EmailAddress, and CreatedDate, and then a Journey using the API Event Entry Source with that Data Extension. Add a simple workflow to the Journey and activate.
-Run a REST API call against the "/interaction/v1/events" route with a CreatedDate value of, for example, "2019-07-11T17:32:00Z" and check date values inserted into DE.
Utilize a numerical offset e.g , +0000, -0100 , +0100, for the date value to convert to UTC time.
Reported By (1)
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.