We have BIX extracts created for both Work class and History of Work class with checking "Use last updated time as start" checkbox so that extract will be incremental daily with no other filter. And a Job scheduler is created which will run BIX extracts daily at 12 AM. We are facing issue of missing afew instances in Work class extract but present in History extract for the same day. To be precise a work object created in the evening and afew rows are created in History but when the BIX extract is pulled for that day on the both the Work and History of Work class respectively sometime the instance is present only in History Extract and missing in Work extract, but receiving the missing instance in the next day extract of Work class.
This is only for afew instances, please can someone let me know if am missing anything.
When using the 'Use Last Updated Time as Start' option, the extract pulls all the data that was updated since the last time the extract ran, up to five minutes prior to the start of the extract. This is performed to avoid issues, where work may be updated while the extract was running.
In your case i believe the instances missing in your work table must have been updated some where in between 11:55 PM - 12:00 AM. So it i not being pulled in today's extract but will be considered for next days extract. History table will not have any updates so it is pulling the instances in todays extract.
If you dont want to consider this 5min Delay:-
Instead of using 'Use Last Updated Time as Start' option, Add a filter using a DateTime property (as required) and specify the value of Last Extraction Time. At runtime, this value is replaced with the date and time when the extract rule last ran based on any selected DateTime property.