https://bugs.kde.org/show_bug.cgi?id=315072
--- Comment #55 from Mike Wolfe <wolfe...@gmail.com> --- "Do you mean transactions which have already been imported are imported again as new transactions instead of being detected as duplicates?" Yes. "If this is the case, can you confirm that the IDs are really the same?" Yes, they are the same. I'm using the <FITID> field to judge this, and they're consistent between updates. "What happens if you import twice in a row - where you should get an identical set of transactions each time." Yes, I do. "Would you expect all transactions to be detected as duplicates the second time? Are they all imported as new transactions?" There are five transactions posted in the last four days that I'm updating with. Four are matched (transaction turns green) and one is unmatched (transaction added in yellow). Matching and accepting them works, but next time I update the same thing happens. I would expect (without knowing how the software is written) that transactions with matching FITIDs (and several other fields) would be ignored for an import. I don't know if this is what KMyMoney is written to do, but maybe it should be? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
