7
Dual write is changing all date fields to either 1/1/1900 or 1/1/1753 during the initial sync. This is changing our live order data, and supposedly by design. We need a fix.
Case details:
Issue reported: Null dates from FO are being shown as 1/1/1753 or 1/1/1900 once the data is loaded to CE via initial sync
Regarding your support request, the reported issue is a known issue which has been confirmed by the product team that it is by design
and if there is null date written to CE, it will be set with a default value 1/1/1900 . By design the system fills the null date in CE with 1/1/1900 and also Null dates on FO is also set to display as 1/1/1753 by default.
Case details:
Issue reported: Null dates from FO are being shown as 1/1/1753 or 1/1/1900 once the data is loaded to CE via initial sync
Regarding your support request, the reported issue is a known issue which has been confirmed by the product team that it is by design
and if there is null date written to CE, it will be set with a default value 1/1/1900 . By design the system fills the null date in CE with 1/1/1900 and also Null dates on FO is also set to display as 1/1/1753 by default.
STATUS DETAILS
Needs Votes