GnuCash
Contact   Instructions
Bug 796579 - Cannot go forward with empty duplicates screen
Summary: Cannot go forward with empty duplicates screen
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Import - QIF (show other bugs)
Version: 3.1
Hardware: Other Mac OS
: Normal critical
Target Milestone: future
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-13 11:00 EDT by Fuuga
Modified: 2020-03-29 18:59 EDT (History)
5 users (show)

See Also:


Attachments
Screenshot of QIF import (104.73 KB, image/png)
2018-06-13 11:00 EDT, Fuuga
no flags Details

Description Fuuga 2018-06-13 11:00:48 EDT
Created attachment 372669 [details]
Screenshot of QIF import

Next button is not active in 'Select possible duplicates' screen if there is nothing in the lists.
Comment 1 John Ralls 2018-06-16 13:51:45 EDT
Can you attach the offending QIF? I think that I fixed this as part of fixing Bug 795272 but I'd like to test it to be sure.
Comment 2 Fuuga 2018-06-17 04:53:07 EDT
@jralls, I wouldn't like to attach it publicly since its real and, in addition, my wife's transactions. Is there any way to restrict an access to an attachment just to some person(s)?
Comment 3 John Ralls 2018-06-17 10:10:06 EDT
You can email it to me privately, jralls at ceridwen dot us.
Comment 4 John Ralls 2018-07-13 13:55:28 EDT
That took a while, first for me to clear the desk enough to work on it but also to track down the problem.

There were two unrelated problems: First, the exception handler that parses the file failed to recognize that parsing had failed and let the assistant proceed to the matching step with bad data. There wasn't useful information to match so that just failed. That was actually fixed as part of bug 795272. Second, the handling for transactions with none of category, payee, and memo (there were two such in your file) raised the exception that the first problem failed to catch. That's fixed as well and I'm able to successfully import your problem file.

The fix will appear in GnuCash 3.3.
Comment 5 Christopher Lam 2020-02-21 19:44:19 EST
> Second, the handling for transactions with none of category, payee, and memo (there were two such in your file) raised the exception that the first problem failed to catch. That's fixed as well and I'm able to successfully import your problem file.

For posterity, can you recall which field was empty?
Comment 6 Christopher Lam 2020-03-29 18:59:32 EDT
Note: refixed in https://github.com/Gnucash/gnucash/commit/1d9c51d8

Note You need to log in before you can comment on or make changes to this bug.