GNOME Bugzilla – Bug 491174
OFX Import binds against wrong account
Last modified: 2018-06-29 21:53:20 UTC
Please describe the problem: When importing an OFX download, it is not bound to the correct account. It is always bound to the oldest checking account, not the one specified in the OFX file. Steps to reproduce: 1. Make two bank accounts 2. Import an OFX into the first 3. Try to import an OFX into the second (These steps are only a guess, I've imported some hundreds of times to the older account before, who knows if there is threshold that must be reached). Actual results: The OFX import is bound to the oldest checking account in the gnucash file, not the one specified (via account number) in the OFX file. Expected results: The OFX import should be bound to the checking account with matching acccount number. Does this happen every time? Yes Other information: I recently added a second checking account to my gnucash file. When I download OFX files from my bank, gnucash insists on associating the OFX import with my oldest checking account, instead of the new one that it belongs with. 1. I've checked the OFX contents and everything seems OK. 2. I can download and import an OFX file for the oldest checking account, and everything seems to work OK. 3. If I open up the OFX file (to the new account) and scrape out the <ACCTFROM> container, gnucash will ask which of my Asset accounts it belongs to, I can select the new checking account, but this 'binding' appears to only affect the first one or two entries in the OFX dialog interface window. Furthermore, the OFX dialog interface window isn't being completely rendered, there are missing lines and such. All this sounds very similar to what was described on gnucash-user about a week ago: https://lists.gnucash.org/pipermail/gnucash-user/2007-October/022056.html I cannot rollback to a 2.0 version of gnucash, because it seems 2.0 cannot read the 2.2 file format. As it is, I'm stuck (outside of hand entry of the OFX, which is a particularly loathesome idea since OFX has worked so splendidly in gnucash up until now).
Oh yeah, I submitted a similar BUG against the debian (testing) gnucash package. Wasn't sure which was the "right place", so I chose both.
I tried the <slot> removal fix from BUG 98963 and this seems to have done the trick. The old checking account had an online_id which was just whitespace. Perhaps this was throwing things off inside of GnuCash.
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=491174. Please continue processing the bug there and please update any external references or bookmarks.