On Feb 8, 2009, at 3:20 AM, Simon Ruggier wrote:

> Hi, see the attached patch. This repairs the ability for the
> transaction import dialog to retry automatches for each transaction
> being imported.
>
> Simon
> <0002-Repair- 
> automatch_store_transactions 
> .patch>_______________________________________________
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel


This patch has some nasty side effects. It tries to change assigned  
target accounts on the fly within a single import. If I have several  
ATM deposits in one import, most of them will come up assigned to the  
last assignment from a prior import. When I change the first one to  
its proper account, your patch results in the rest of the deposits  
also being assigned to the account just entered. That's not so good,  
but not the end of the world (and definitely not what gnucash has done  
in the past). The problem comes when I try to correct the account  
matched to the second deposit. Sometimes (most but not all) the  
matcher goes back and reassigns the first deposit to the wrong account.

I don't think the problem is locked in a circular change cycle, but it  
sure makes the matching process a pain.

Dave
--
David Reiser
dbrei...@earthlink.net




_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to