[GNC] suddenly will not accept a normal transaction in a batch import.

[arthur brogard]

I used to get them all the time until I switched off Bayseian matching after someone here suggested it.
Years ago now, I think.
Now it is rare.  For instance 2000 transactions imported in one batch the other day.  No red lines at all.
That's what makes me keen to discover just what is going on here.  It seems to have no rational cause.
:)

 

    On Tuesday 5 May 2026 at 02:11:38 am ACST, David Carlson <david.carlson.417 at gmail.com> wrote:  
 
 I get those red items all the time.  Just change them to whatever you know is correct.  If you are unsure of which account to assign the transfer to, just call it new and remember to double check after the import is complete.
On Mon, May 4, 2026 at 12:08 AM arthur brogard via gnucash-user <gnucash-user at gnucash.org> wrote:

yep. i'm doing that.  i have a litte 12 transaction csv i keep playing with.  6 are the ones it barfs at.  6 are accepted.
i move fields around and whatnot.  haven't come up with an answer yet.
tested the proposition that it is just discerning existing transactions: no, that's not it. I just offered it half a dozen existing trans and it was willing to take them.  
one of my tests I simply moved the amount column down one row.  then put the bottom figure at the top.  making 6 new transactions with all the old data fields.  It accepted all except one.  was willing to accept  (i didn't go through with it).
did it again with amount+desc this time. same thing.  and so on.. playing like that.
put them back where they came from: bang: rejects...It's a puzzle.


    On Monday 4 May 2026 at 02:30:14 pm ACST, Steve Butler <stephen.m.butler51 at gmail.com> wrote:  

 You can make a copy of your file and test the import there making various changes to see what happens.
On Sun, May 3, 2026, 20:19 arthur brogard <abrogard at yahoo.com> wrote:

So certain?  That's it?  It claims this is an existing transaction already in the books?
What does it mean 'force them to be loaded'?  It means I want the transaction entered?
If it makes my query any clearer I am talking of transactions taken directly from bank statements electronically and verified. So i am 100% confident every one is unique.
You seem to be saying gnucash will barf at apparent duplicate imports of a transaction.  I wondered about that.  That's good.  If I'm reading this right then that's what we have here - the mechanism for identifying possible duplicates?
That's what it is all about?
And if I insist on 'load' then it will enter them?
hey..  thanks for the reply...  :)



    On Monday 4 May 2026 at 10:50:10 am ACST, Steve Butler <stephen.m.butler51 at gmail.com> wrote:  

 The importer thinks it sees them already.  So if you want to force them to be loaded, then click the box in the first column.
On Sun, May 3, 2026, 18:13 arthur brogard via gnucash-user <gnucash-user at gnucash.org> wrote:

I have six transactions that gnucash will not import.  It red highlights and says 'do not import; no action selected'
hundreds of such transactions have been imported without any action selections at all.  I give, of course, date, amount,description, destination account.  All works fine.  Except for these six.

Any clues?  Thins I could/should do?  
_______________________________________________
gnucash-user mailing list
gnucash-user at 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.



_______________________________________________
gnucash-user mailing list
gnucash-user at 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.



-- 
David Carlson