[Kmymoney-devel] [Bug 225550] Import does not set detail field correctly

Antony antony.jamin at ieee.org
Wed Feb 10 16:05:17 CET 2010


--- Comment #4 from Antony <antony jamin ieee org>  2010-02-10 16:05:14 ---
My apologies for not following this up earlier.

After numerous experiment at importing different QIF files into different KMY
files, I have finally got this problem sorted. 

Also I cannot confirm it, I believe I know what the problem was. At some point
a blank payee got added to KMY file and the default option is to match
transaction automatically. The QIF file I tried to import had P fields
containing 2 consecutive white spaces in the middle of the description. When
importing, the matching process identified these payees as identical to the
blank payee already in the KMY database and automatically replaced those payee
by a blank payee.

While the new matching feature confusing me for some time, I am not quite sure
if this is the expected behaviour. I leave you the decision on whether this bug
must be close without further investigation or not.

Thank you for your help with this. KMyMoney is a great application, thank you
to all of the contributors!

Antony J.

PS: While trying to follow you suggestion about using the anon-xml, I noticed
that unfortunately the Save-as command crashed KMyMoney every time I used it.
Unfortunately, my system could not collect enough debug infos to report it in a
useful way. I'll check if this has already been reported.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the KMyMoney-devel mailing list