Good information and very readable code on Bayesian matching -
https://wiki.gnucash.org/wiki/Bayes
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
Hi,
flywire writes:
> Agree that import works in small chunks (as posted previously). Does that
> response cover any way of getting GUIDs on the data?
The GUIDs are 100% internal to GnuCash and unique per user per object
(account, transaction, etc). There is no way to add GUIDs to imports,
A quick look through a copy of the data file suggests that it is somehow
incorporated in the data for the Bayesian matching for an account but I
can't be sure without looking through the code. I use Bayesian matching
rather than the older import name mapping which can be used optionally.
It is
Unfortunately knowing the GUID's won't help as the importer currently doesn't
import them and use them directly only via that mapping process.
-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
On 4/26/20 6:18 PM, flywire wrote:
>> Do you know other (including closed source) apps don’t use something
> similar?
>
> I've used many other financial apps that just import Transfer Account
> directly in as listed in the csv.
>
>> Why would a user normally need to know this implementation
> Do you know other (including closed source) apps don’t use something
similar?
I've used many other financial apps that just import Transfer Account
directly in as listed in the csv.
> Why would a user normally need to know this implementation detail?
Because it's counter-intuitive to load a
> On Apr 26, 2020 w18d117, at 7:28 PM, flywire wrote:
>
> @Tom Seesink - Will you log that as an enhancement bug at
> https://bugs.gnucash.org/enter_bug.cgi?product=GnuCash (Import - other)?
> Please link back here.
>
> @David Cousens, that excellent explanation about how the Import Matcher
>
@Tom Seesink - Will you log that as an enhancement bug at
https://bugs.gnucash.org/enter_bug.cgi?product=GnuCash (Import - other)?
Please link back here.
@David Cousens, that excellent explanation about how the Import Matcher
works helps answer my question. The documentation needs to explain
the
Tom
Please Reply to the gnucash-user@gnucash.org (Reply to List or Reply to All)
mailing list rather than individual
contributors. The issue will get a wider response and the replies are then
useful to all of the list participants.
I am not a major contributor to the development but I think
The import was successful but I imagine the experience is like going
through a binder and reaper blindfolded in the dark. The issues weren't all
GnuCash.
I reduced the form size, imported 50 (?) transactions (into a sqlite file)
and then the rest. The account matching still occurred :(( but the
Mainly because your particular use case is not the only one that the
importing process has been designed to meet and the import process has to
survive at least some common problems in the implementation by various
sources of files and a considerable variety in the amount of information
supplied
I have imported thousands of entries in CSV format--years of
transactions--and found it helpful to split the original CSV into multiple
parts (in my case, by year), saving the gnucash file after each import.
For the very first import of a new bank account, I use a CSV with only three
months of
I have a few thousand transactions in a bank statement csv file tagged with
a transfer account. Why can't I skip the import matching process?
Firstly, assume this test data from the Concepts Guide checking account
with the addition of a typical bank statement description and transfer
account. It
13 matches
Mail list logo
