GNOME Bugzilla – Bug 583269
Unspecified bug when importing QIF file where a record has empty P line
Last modified: 2018-06-29 22:22:00 UTC
Improve the diagnostic message, saying that the problem is due to an empty line Other information: I came across this bug when trying to import a file generated by a script of mine. The file looks like this: --------- !Type:Bank D31/03/2009 P MEnd 31.03.2009 T1.87 ^ --------- GnuCash fails to import this file with the general message "A bug was detected while converting the QIF data".
Confirmed. I can reproduce this in trunk.
*** Bug 619042 has been marked as a duplicate of this bug. ***
Note that this bug is still present in 2.3.12.
Created attachment 177162 [details] console output I am not sure if it is the exact same problem, but I have the same result with 2.4
Created attachment 177163 [details] example qif The L line is empty. When the M line is empty too, the import will succeed.
(In reply to comment #0) > Improve the diagnostic message, saying that the problem is due to an empty line > > Other information: > I came across this bug when trying to import a file generated by a script of > mine. The file looks like this: > --------- > !Type:Bank > D31/03/2009 > P > MEnd 31.03.2009 > T1.87 > ^ > --------- > GnuCash fails to import this file with the general message "A bug was detected > while converting the QIF data". May 2011. This is still a problem. GnuCash V2.2.9 (Ubuntu) r17949M 2010-03-23. It appears when a transaction on a credit card is authorised by a bank and there is a delay before the name of the payee is added. D23/04/11 T-45.35 P M377878401....65 If the statement is downloaded before the payee name is added by the bank, it appears that the lack of any information after the "P" upsets /usr/share/gnucash/scm/qif-import/qif-to-gnc.scm and /usr/share/gnucash/scm/qif-import/qif-to-gnc.scm. I cannot find where this error message comes from but to me it is overkill. If the object is to increase the appeal of GnuCash for anyone trying to migrate from Microsoft alternatives (Quicken), to receive such a 'dead end' message without any suggestion as to what to look for will turn people off. The average user will uninstall GnuCash and go back to what they used previously. Until the coding error is found, can the message be changed to something more helpful and include something such as a web link that has a list of known instances where the code cannot handle the import - i.e "Code cannot handle blank after "P" in QIF File - Delete transaction or add text after the "P" using Gedit or similar"
*** Bug 726220 has been marked as a duplicate of this bug. ***
Still present in 2.6.2 according to bug 726220. That bug has a nice stack trace which can help find the source of the problem.
*** Bug 784381 has been marked as a duplicate of this bug. ***
Reassigning because I didn't hear anything from Chars in the last years.
Charles was meant.
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=583269. Please continue processing the bug there and please update any external references or bookmarks.