PB2019 R2 Build 2353, SQL Server 2014

There seems to be a problem with the ImportJson() function and DateTime/Time columns. If I export a JSON from a datastore and import it into a different datastore (same datawindow object), the current value becomes the original value in the second datastore causing the update to fail with row changed between retrieve and update.

To test this, I created a simple table:

testString  VARCHAR(10)

testDateTime   DATETIME

testDecimal  NUMERIC(10,0)

testLong  INTEGER

testTime   TIME

I added a row with values 'test', 04/02/2021 12:00:00, 123.45, 98765 and 8:00:00.

I created a datawindow object, dw_test, for the table. I created two datastores with dataobject = dw_test. I retrieved the data in datastore1, changed all of the values, and then exported the row as a standard JSON. I imported the JSON into datastore2. Attached are the resulting JSON strings. BeforeJson is the export from datastore1. AfterJson is the export from datastore2. If you compare the original values, you will see the DateTimeTest and TimeTest column now have the current value as the original value in AfterJson.

Is this a bug or expected behavior? 

Thanks

Joe