RPL: Custom Date Field Personalized With Wrong Timestamp for Account Outside of PDT
(Doc ID 2178897.1)
Last updated on NOVEMBER 26, 2024
Applies to:
Oracle Responsys Marketing Platform Cloud Service - Version 6X to 6X [Release 6x]Information in this document applies to any platform.
Symptoms
Custom date fields stored in Profile Extension Tables or Supplemental Tables are being personalized with an incorrect offset. This is occurring for accounts outside of the Pacific Timezone.
For example: An account with the timezone EDT is attempting to personalize a custom date field, REGISTRATION DATE. This date is saved in a Profile Extension table with the timestamp, 09/01/2016 21:00. When this field is personalized, the campaign is displaying 09/02/2016 00:00. This is not correct and potentially changes the date to the next day. This can be very problematic depending on what this custom date field represents.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |