Solving duplicate data issue with Offline data import (TransactionID) - any ideas? Hi all,I would be thrilled if somebody would be able to come up with some suggestions on how to solve a "challenge" we are facing.Backround:- we are using offline data import to add some offline events and evars to our reporting- we are using transactionID to associate these with user behaviour- the events are set as countersThe challenge:- we were running a few imports of offline events to Adobe these past few weeks, all in all, 3 months worth of data- by a mistake, we uploaded the the whole database everytime, not only the incremental data :(- we found out, that every event that we uploaded as a duplicate by a mistake is treated by adobe, as if it happened multiple times, and not as a duplicate of the same event- so, if an event with the same transactionID and the same timestamp was included in three offline data imports, Adobe treats it as if it happened three times- obviously, the data is ruined- obviously, we would love not to loose 3 months worth of data- it is not possible to r