[GNC] OFX Import with Investment Transactions

[Robin Chattopadhyay]

Ubuntu 20.04 LTS (VMWare virtual machine in case that matters)
Gnucash 4.8
libofx 0.9.15

I tried importing an OFX file from my 401K provider this morning and I got
a message box that said it had imported 2 transactions for a single
security in the file and there were no additional transactions to process.
This was incorrect as there were 18 new transactions across nine securities
(along with a number of other transactions that had already been imported
previously).

I tried a number of things to resolve (after taking a backup, of course):
1 - Tools > Import Map Editor and deleted all of the associations for this
file. When I re-imported, I was prompted to map each security in the file
to the correct account. No issues there. But when importing the OFX file
again, I had the same experience as described above
2 - Created a blank file and attempted to import the file there. Through
the import process, I created new securities and new accounts, nothing
unexpected there. Then the generic transaction importer dialog popped up,
but with just the two transactions for the same security cited in the
original problem dialog. I imported those, clicked OK and then the generic
transaction importer dialog came up *again* but only with transactions for
a single, different security. I imported those and repeated the process for
each security with transactions in the file. Each time the generic
transaction importer dialog came up, it only had transactions for a single
security. This is definitely new behavior that I didn't see in 4.6.
Previously the import dialog had all the new transactions in the file
3 - Reverted to 4.7. Crashed when selecting Import from the File menu
(Trace/breakpoint trap (core dumped). Not unexpected, but thought I would
try anyway.
4 - Reverted to 4.6. This works as it used to with all the new transactions
in a single dialog

Finally, I don't know if this matters, but I scanned stdout from the
build/make/install process to see if anything looked obviously wrong and I
found this (I don't know if it's relevant):

-- Performing Test HAVE_OFX_BUG_39
-- Performing Test HAVE_OFX_BUG_39 - Failed

Thanks,
Robin