https://bugs.kde.org/show_bug.cgi?id=369448
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ostroffjh@users.sourceforge
| |.net
--- Comment #2 from Jack <ostrof...@users.sourceforge.net> ---
I can confirm this is the problem. In a downloaded qfx file, BOA uses
something like
<FITID>201609101 but in a direct connect download, it uses
<FITID>D2016254T1048539. There are other differences also (at least in my
example) such as the file not including the <MEMO> (which in the direct connect
seems only to be part of the <NAME> anyway, but it is the FITID difference that
causes KMM not to recognize the duplicate transaction.
Unfortunately, I predict 0% chance of getting BOA to fix this, since it seems
absolutely impossible to talk to anyone who knows anything and can do anything
except follow their script. In any case, I'm really curious if anyone has any
idea why they re-enabled direct connect, after going to all that trouble to
discontinue it.
--
You are receiving this mail because:
You are watching all bug changes.
