[GNC] CSV matching produces duplicates?

[Elmar]

Even if I know that the match exists, and I tell it that it does, it 
replies that the match does not exist.  So I have to either leave it red 
so it doesn't import, or accept the duplicate.  Which means keeping both 
windows open (the match window and the account window), and manually 
checking the matches myself.  Which defeats the entire purpose of 
computer matching.

On 3/3/21 6:13 PM, David Carlson wrote:
> Isn't it still possible to manually override the automatic behavior on 
> a transaction by transaction basis during the various types of imports?
>
> I know that is not wanted, but that is what we have to do to train the 
> Bayesian matching.  I am frustrated that the new matcher released in 
> the 3.x series is not learning to make matches that it did very well 
> in the old matcher.  If anyone has suggestions in this regard I am all 
> ears.
>
> On Wed, Mar 3, 2021 at 4:46 PM Elmar <etschme at gmail.com 
> <mailto:etschme at gmail.com>> wrote:
>
>     No - just taken from the bank as CSV directly.  I have another post
>     where the OFX problem is described.
>
>     On 3/3/21 5:40 PM, Christopher Lam wrote:
>     > You mean transactions imported via ofx then reimported with CSV?
>     This
>     > may be https://bugs.gnucash.org/show_bug.cgi?id=798128
>     >
>     > For now, it'll be best to narrow down your CSV import to exclude
>     the
>     > already imported date range.
>     >
>     > On Thu, 4 Mar 2021, 5:59 am Elmar, <etschme at gmail.com
>     <mailto:etschme at gmail.com>
>     > <mailto:etschme at gmail.com <mailto:etschme at gmail.com>>> wrote:
>     >
>     >     Version 4.4 from flatpak on linux mint 19.3  ( I think my sig
>     >     needs to
>     >     be fixed, but I misremember how to do that)
>     >
>     >     Since my OFX import to my bank seems now broken, I have been
>     >     reduced to
>     >     CSV imports.  And I find that the matcher does not match
>     worth beans,
>     >     producing duplicates of tranasctions that in fact DO match
>     within the
>     >     one month window.  Is this a know problem?  Is there a way
>     to tune
>     >     the
>     >     matcher better? - Elmar
>     >
>     >
>     >
>     >     _______________________________________________
>     >     gnucash-user mailing list
>     > gnucash-user at gnucash.org <mailto:gnucash-user at gnucash.org>
>     <mailto:gnucash-user at gnucash.org <mailto:gnucash-user at 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.
>     >
>
>     _______________________________________________
>     gnucash-user mailing list
>     gnucash-user at gnucash.org <mailto:gnucash-user at 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