Skip to main content
To homepage To homepage
Question

Incremental loading issue - New Primary Key insert with Older DateLastModified timestamp than latest

  • July 29, 2026
  • 1 reply
  • 2 views
K
Contributor
Forum|alt.badge.img

Version: TX 7158.1

Hello,

I’m currently running into an incremental loading issue where the source system automatically generates invoices in batches. This inserts new rows/Primary keys in the invoice table. It could be that certain invoices are scheduled for a batch. Let’s say from 24-07-2026 scheduled for 29-07-2026.

If that’s the case, the new row will get inserted on 29-07-2026 with a datelastmodified of 24-07-2026. Any changes to that document will trigger the datelastmodified correctly, only this process gives this issue. In that case, my incremental loading will completely miss these new document / primary keys (currently -1 day offset).

Is there a way to always add new primary keys but only do the updates based on the datelastmodified timestamp?

1 reply

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • July 29, 2026

Hi,

in that case your datelastmodified is not really the mutation date - either a “better” field should be used for the incremental selection rule or a reasonable subtraction should be applied in the incremental rule. That would mean checking with the business what the longest time between invoice batches would reasonably be and subtracting that in the incremental setup.

Terms and ConditionsAccessibility statement