Today we have faced issue where we are running a mapping task for reading the data from SF object from 3 am to next day 3AM and loading it to a table . during the job run the SF record got an update from SF end and the same updated information has flown down to the table. is this an expected behavior of a sales force connection . Ideally that record should have hold older time stamp due to the update happening at job running time update time stamp value is getting passed to target . Any one came across the similar issue?
example as shown below :
The timing details of mapping task execution 9/17/2019 05:35 AM – 05:41 AM GMT .
The first update on the record was at 2019-09-17 01:29 AM GMT
mapping filter conditions are : (LastModifiedDate >= 2019-09-16T04:00:00.000Z and LastModifiedDate < 2019-09-17T04:00:00.000Z)
salesforce update time : 2019-09-17 05:39 AM GMT
expected value at target is : 2019-09-17 01:29 AM GMT
Value Loaded in target is : 2019-09-17 05:39 AM GMT which is latest updated value of the record which happen during the session run time from sales force end .