Workday synchronization is updating every Employee record (4383134)

Workday synchronizations processes every employee and updating each record for DateLastWorked and Exitdate, even when they are blank. 

The minimum date in Identity Manager is 1899-12-31. That value has the meaning "not defined". If a datetime value in the database has NULL, the object layer interprets this as 1899-12-31. It's not possible to save an older date over the object layer in OneIM.

If this is attempted, the value will be converted to the minimum date and will be NULL during the saving to the database. The sync engine handles the value "0001-01-01 00:00:00" as "undefined".

If both sides of the sync had an "undefined" value, there would not be a difference, and the sync would not correct it. The problem is, that the target system does not have that "undefined" value, because it contains a time: "0001-01-01 05:00:00".

For the sync engine, that's a valid datetime (it's not "undefined") and therefore it corrects the value in OneIM.

WORKAROUND: Add a condition to the mapping rule that  makes sure that the rule will be executed only if the value on the target system side is greater than the minimum date in the database.

Example: Right.EndDate > 1900-01-01

STATUS: Enhancement Request 700603 has been submitted to the Product team for consideration in a future version of  Starling Connect and Identity Manager.