On 2013.02.13 09:52, Michael Wolfe wrote:
On 2/9/2013 3:44 PM, Łukasz Maszczyński wrote:
2013/2/7 Michael Wolfe <wolfe...@gmail.com>:
On 2/6/2013 9:45 AM, Łukasz Maszczyński wrote:
Problem did NOT show up today when I tried to update; everything
appears to
be working now (just as I had the bug report mostly filled out!).
I did NOT
update or recompile since yesterday.
Hmm, then most probably the content of OFX changed in the meantime
(one download different than the other), which would explain why you
observed the problem for a short time only. My guess is that the
transaction's bankId-s were messed up, in that case you wouldn't even
see the difference, but the application would interpret the
transactions in a bit different way.
One way or another - the OFX file you sent me looks fine, and
importing it multiple times does produce desired result - transaction
duplicates are found and matched. If you ever see the problem again,
please save the broken OFX and send us the anonymized version of it.
Hello again. It has happened again, and I've filed a bug report
(315072 <https://bugs.kde.org/show_bug.cgi?id=315072>) with an
attached OFX log. Thanks for the interest!
Compare the OFX log from two different downloads. If they match
(except for timestamps) then there is a real bug. On the other hand,
if something like the bankId's don't match, then KMM/libofx is behaving
correctly and you need to figure out why your bank is changing the
transaction ids each time.
Jack
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
