Re: [GNC] Import bug? no account matching options
I am confused about Account ID vs Transaction ID as used in this thread. They are not the same, and transaction ID would not be used for account ID purposes anyway. I have Chase OFX files that have Account ID's but no transaction ID's that, so far, have imported fine for me, except I never noticed that some transactions should be missing from imports with overlapping date ranges because I never download overlapping files. Yes, transaction ID's should be present, but GnuCash doesn't crash if they are missing from OFX files, at least in older 2.6.x releases. For QIF files, is the problem with the source account ID which only appears at the beginning of the transaction list or with the 'transfer' account in each transaction? I think account ID is optional in QIF files. David Carlson On Fri, Sep 27, 2019 at 11:08 PM Liz wrote: > On Fri, 27 Sep 2019 07:18:21 -0400 > David Reiser via gnucash-user wrote: > > > > I have no experience with Chase, but my bank does not use unique > > > transaction ID codes in their OFX files. > > > > > > Liz > > > > Then they aren’t standards-compliant ofx files. Gnucash doesn’t > > display them anywhere, but they are stored with the transactions. Dave > > -- > > > I know that, but I have not succeeded in getting the bank to change (so > far). > > Liz > ___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > -- David Carlson ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
On Fri, 27 Sep 2019 07:18:21 -0400 David Reiser via gnucash-user wrote: > > I have no experience with Chase, but my bank does not use unique > > transaction ID codes in their OFX files. > > > > Liz > > Then they aren’t standards-compliant ofx files. Gnucash doesn’t > display them anywhere, but they are stored with the transactions. Dave > -- I know that, but I have not succeeded in getting the bank to change (so far). Liz ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
> On Sep 27, 2019, at 02:36, Liz wrote: > > On Thu, 26 Sep 2019 19:20:17 -0400 > David Reiser via gnucash-user wrote: > >> Another workaround would be to download QFX files instead. That has >> the added advantage that if you do it more than once per billing >> period, the presence of the unique transaction ID makes it trivially >> easy for the import matcher to throw out duplicates without even >> having to ask you about them. >> >> Dave > > I have no experience with Chase, but my bank does not use unique > transaction ID codes in their OFX files. > > Liz Then they aren’t standards-compliant ofx files. Gnucash doesn’t display them anywhere, but they are stored with the transactions. Dave -- Dave Reiser dbrei...@icloud.com ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
On Thu, 26 Sep 2019 19:20:17 -0400 David Reiser via gnucash-user wrote: > Another workaround would be to download QFX files instead. That has > the added advantage that if you do it more than once per billing > period, the presence of the unique transaction ID makes it trivially > easy for the import matcher to throw out duplicates without even > having to ask you about them. > > Dave I have no experience with Chase, but my bank does not use unique transaction ID codes in their OFX files. Liz ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
> On Sep 26, 2019, at 4:41 PM, Grant wrote: > I'm trying to import transactions I've downloaded from Chase in a QIF file but when I'm importing Gnucash doesn't give me any options to match them to an account (zero accounts in the list) and the button to change the matched account is grayed out. This is happening with 2 separate Chase accounts and I am able to import transactions from another bank just fine. What could be causing this? >>> >>> Lack of L lines in the transactions? >> >> >> I just figured it out. Chase uses a blank line instead of a line >> containing only the "^" character to separate transactions. I'm using >> this to strip the top blank line: >> >> sed -i '/./,$!d' file.qif >> >> and then this to replace all blank lines with the "^" character: >> >> sed -i 's/^[[:blank:]]*$/^/' file.qif >> >> That seems to work. Surely the Chase files are out of spec but is >> this something Gnucash could work around? If so I'll file a bug. > > > Here's what the problem/bug looks like: > > https://imgur.com/a/vPZOdD2 > > The import dialog skips the "Set a date format for this QIF file" and > the "Set the default QIF account name" sections. > Another workaround would be to download QFX files instead. That has the added advantage that if you do it more than once per billing period, the presence of the unique transaction ID makes it trivially easy for the import matcher to throw out duplicates without even having to ask you about them. Dave -- Dave Reiser dbrei...@icloud.com ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
> > > I'm trying to import transactions I've downloaded from Chase in a QIF > > > file but when I'm importing Gnucash doesn't give me any options to > > > match them to an account (zero accounts in the list) and the button to > > > change the matched account is grayed out. This is happening with 2 > > > separate Chase accounts and I am able to import transactions from > > > another bank just fine. What could be causing this? > > > > Lack of L lines in the transactions? > > > I just figured it out. Chase uses a blank line instead of a line > containing only the "^" character to separate transactions. I'm using > this to strip the top blank line: > > sed -i '/./,$!d' file.qif > > and then this to replace all blank lines with the "^" character: > > sed -i 's/^[[:blank:]]*$/^/' file.qif > > That seems to work. Surely the Chase files are out of spec but is > this something Gnucash could work around? If so I'll file a bug. Here's what the problem/bug looks like: https://imgur.com/a/vPZOdD2 The import dialog skips the "Set a date format for this QIF file" and the "Set the default QIF account name" sections. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
> > I'm trying to import transactions I've downloaded from Chase in a QIF > > file but when I'm importing Gnucash doesn't give me any options to > > match them to an account (zero accounts in the list) and the button to > > change the matched account is grayed out. This is happening with 2 > > separate Chase accounts and I am able to import transactions from > > another bank just fine. What could be causing this? > > Lack of L lines in the transactions? I just figured it out. Chase uses a blank line instead of a line containing only the "^" character to separate transactions. I'm using this to strip the top blank line: sed -i '/./,$!d' file.qif and then this to replace all blank lines with the "^" character: sed -i 's/^[[:blank:]]*$/^/' file.qif That seems to work. Surely the Chase files are out of spec but is this something Gnucash could work around? If so I'll file a bug. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Import bug? no account matching options
Hi, Grant writes: > I'm trying to import transactions I've downloaded from Chase in a QIF > file but when I'm importing Gnucash doesn't give me any options to > match them to an account (zero accounts in the list) and the button to > change the matched account is grayed out. This is happening with 2 > separate Chase accounts and I am able to import transactions from > another bank just fine. What could be causing this? Lack of L lines in the transactions? If there are only P and M lines, but no L lines, the importer will only ask you to map Payees/Memos to accounts, but not Qif Accounts. Of course, without seeing an example of the QIF I can't be sure. > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
