On 12/18/18 3:31 PM, Steve Cohen wrote:
Thanks.
Seems like none of these solutions will work if your data is stored as
a .gnucash file, they only work with .xml files.
Is there a way to convert this?
Is the Bayesian matching applied to entries that are corrected in the
account editor, or is it only applied to entries made in the importer?
I am somewhat comfortable with the bleeding edge, but, when is the
release of version 4 expected?
On 12/18/18 5:17 PM, David Cousens wrote:
Steve
These may help.
https://wiki.gnucash.org/wiki/Bayes
https://lists.gnucash.org/pipermail/gnucash-user/2016-July/066299.html
http://gnucash.1415818.n4.nabble.com/Fixing-confused-bayesian-matching-data-td4685819.html
http://blog.jdlh.com/en/2016/07/29/resetting-gnucashs-import-transaction-matching/
Make a backup of your data file and only work on a copy until you are
sure
it is working after changing it if you attempt any of the solutions
mentioned in the above posts.
The importer stores the map data and probabilities during the final
step of
the import process. If you let transactions go through to Imbalance
then it
obviously gets no data to work with. If you assign all transactions to a
specific transfer account before import and continue to do that, it will
eventually correct itself. There are a few situations in which the
bayesian
matcher does not work. I find where there is a transaction unique number
which changes with each periodic transaction the matcher seems to run
into
problems. An number identifying the payer/payee and not the transaction
itself is OK. Some of mine have both.
There will be a feature to be added in GnuCash V4 which allows multiple
selection of transactions and assignment of a single transfer account
in the
import matcher which speeds up the transaction matching process
significantly. It can be incorporated in V3.x as a patch if you build
GnuCash from source, but the risk is that future bug fixes in the
importer
which change the two affected files could result in a non-working
GnuCash.
It incorporated in the master barnch of the GitHub repository and can be
built from that if you are comfortable working with the bleeding edge.
David Cousens
-----
David Cousens
--
Steve,
In GnC, click on the Tools menu and then on the Import Map Editor. Once
on the new screen you can see all the mappings that have been generated.
In my case, I did some restructuring of my accounts and found that the
existing mappings no longer worked. I highlighted the top levels and
clicked on the DELETE key. That reset everything for me and I'm in the
process of building the new set of mappings.
The high level is based on the imports you do. I had three: Checking
account, Credit Card, and Savings account. The last one is used so
little that it isn't worth the hassle of downloading the 1-2 entries
each month so I now enter them by hand. That will leave me with just
two imports -- which I plan to do multiple times each month to keep the
number of transactions low.
Anyway, if you decide to clear everything out, the above is a nice and
easy way to do that.
--Steve
--
Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
-------------------------------------------
GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
_______________________________________________
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.
