Sure. I am not using AqBanking, my problem is with CSV import. I did notice those errors/warnings in the log but I could not immediately find anywhere to turn aQbanking off. I know I had tried at one point to experiment to see if my bank somehow showed up, it didn't, and I have never used it for anything. It is of course possible something lingers from that.
Attached are three files:
test.gnucash - a very simple book (based on the simple check book template)
abc.csv - two transactions (already imported into test.gnucash)
def.csv - two more transactions (not yet imported)
def.csv is formed from abc.csv, just with dates and amounts modified
such that gnucash would not think they can reconciled. It is therefore
otherwise the very same transactions and I would expect matching to
occur.
As abc.csv has been imported, test.gnucash contains the import settings
(named "test") that I am using.
/Christian
test.gnucash
Description: Binary data
abc.csv
Description: Binary data
def.csv
Description: Binary data
----------------------- On Wed, Apr 26 2023, Geert Janssens wrote: I have tried to look into this, but I don't have enough information to go further. First off, from your logs I infer you are importing data via AqBanking. I have no accounts that are compatible with aqbanking so I can't go that route. Instead I have tried to import data via the generic CSV importer. If I tweak my import data to fall in the bayesian thresholds, it is properly matched this way. So to continue, I will need some test data from you. Can you create a minimal book with a few transactions in it already and a csv file to import in there that should give matches ? Please do change any private data. Additionally, please specify which profile you are using in the Aqbanking importer. Perhaps the easiest is to append all of these in a new bug report. The mailing list is a bit cumbersome to track updates. Regards, Geert Op dinsdag 25 april 2023 21:34:33 CEST schreef Christian Lynbech: > I have now done a few more experiments and is not any less confused. > > So to iterate, using 4.14, automatching works, using 5.0 it does not > work. > > I tried turning on logging as John suggested. When I import to 5.0, I > get nothing logged during the operation. However, when trying to do the > import with 4.14, I am getting a number of warnings like this: > > * 20:07:17 INFO <gnc.import> [GncTxImport::update_pre_split_props] User > warning: Column 'Konto' could not be understood. > > The word "Konto" is danish for "Account". Even so, automatching did > work. I am attaching the log files from the two attempts below. > > I then thought, perhaps this is a language thing (I am using danish both > on my computer and in the books), so I c'tried changing the language to > english but it did change the results, no automatching on verson 5. > Also, the warnings I see in version 4, now was in english (e.g > "Account"). > > I have also tried generating a completely new book, as simple as can be, > but the behaviour is exactly the same, so it is not something something > that has piled up in my actual book. > > Since this does not appear to be a universal issue, it is possible that > it is somehow language related. > > Attached below are the two aforementioned log files, the one named with > "4" is from the 4.14 run (which works) and the one with a "5" is from the > 5.0 version (that is not working). > > I can provide my test book and sample CSV files as well, if anybody > would like to see them. > > Thanks for taking an interest in my issue. > > /Christian
_______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
