On 8/13/21 4:40 PM, Brendan Coupe via KMyMoney-devel wrote:
[snip...and sorry for any strange formatting, I'm not using my usual
email app]
I thought about that since importing CSV files from USAA into KMM is
annoying but it may not save me any time. I may give it a try.
I should have asked if you can export OFX (sometimes call QFX) files
from USAA. That would be better than importing CSV. However my
suggestion (which may well not save any time) is doing a direct connect
import to GnuCash, and then exporting from there to import into KMM.
Valid as a temporary workaround at best.
I guess I wasn't clear. I tried mapping with both ofximporter and
kbanking. kbanking was already setup since it uses the aqbanking
settings that I got to work on GnuCash. The KMM crash happens when I
attempt to import an account that was mapped with kbanking/aqbanking.
I tried expert mode (ofximporter) before my first email. I tried both
QMOFX and 2300 in the "Identify As" box. Both failed. Both appear to
be required in aqbanking but ofximporter only has one box to fill in.
From the GnuCash instructions:
Application ID QMOFX
Application Version 2300
Header Version 103
Aha - in that single box, you need to put QMOFX:2300 - it combined the
appid and version, separated by a colon.
The exact same settings (QMOFX & 2300) in AqBanking work in GnuCash
but cause KMM to crash. Does AqBanking work normally, I've never tried
to use it before today.
We should certainly track down the cause of that crash, but getting you
importing again is also good, if a separate goal.
Jack
