Share
Report
7Hi We created a daily export of payments based on the DEX_ROW_TS field in the PM30200. We initially selected the payments as of a date, and saved the timestamp of the last record exported, so the next day we export transactions with DEX_ROW_TS > savedtimestamp.
The testing went great, but when we moved to production we keep getting a lot of other payments in the daily exports, and it's due to the DEX_ROW_TS getting updated. According to the documentation found, there's only a trigger on update on this table to update the DEX_ROW_TS field. The question is: what type of activities could be causing this timestamp to change if the users claim they haven't applied/unapplied records to the payments that are getting a new timestamp?
thanks in advanced for your help!
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
