Fire Journey Event REST Endpoint does not respect UTC time conversion when using 'Z' zone designator

Summary 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.

Repro -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.

Workaround Utilize a numerical offset e.g , +0000, -0100 , +0100, for the date value to convert to UTC time.

Source: Salesforce.com

Powered by NewsAPI.org

Keywords:

ISO 860 • UTC offset • Server (computing) • Time • Data • Source code • Data • Filename extension • Graph (discrete mathematics) • Workflow • Execution (computing) • Representational state transfer • Subroutine • Human–computer interaction • Computer simulation •