0
Fixed

Unexpected timestamp IdB connector behaviour for 12/31/9999 23:59:59

Bob Bradley 4 years ago • updated by anonymous 3 years ago 2

As per attached email:

Adam
When investigating why my adapter join wasn’t pulling through any data I noticed the following:

Note how the startDate format varies from the endDate. Checking the schema both columns are configured as “timestamp”:

Is it possible that the value “9999-12-31T23:59:59Z” exceeds the bounds for this datatype in IdB?

The following is the raw data for the record in question (via the same PowerShell script that loads the connector, but running in debug mode) where both fields are represented as valid datetime values:

seqNumber : 1
userId : 10000167
startDate : 10/01/2014 00:00:00
endDate : 12/31/9999 23:59:59
businessUnit : U
company : AU01
countryOfCompany : AUS
lastModifiedOn : 10/07/2014 09:24:36
lastModifiedDateTime : 10/06/2014 22:24:36
userNav.userId : 10000167
positionNav.code : 50000355
positionNav.effectiveStartDate : 10/01/2014 00:00:00
employeeTypeNav.id : 12088
employeeClassNav.id : 1875
emplStatusNav.id : 1581

Thanks
Bob

Note: initial assessment only and possible workaround suggested if there turns out to be an issue here


image1.png
image2.png
Affected Versions:
Fixed by Version:

Resolved. It was an issue with the transformation configuration.

IDB-1182 created for the DateTime format.

Confirmed transform now OK - date issue is just a minor UI bug