Quickfill Issues

[David T.]

So, to summarize the Quickfill status, one can:

1) Accept incoming transactions as is, WITH ALL CAPS AND (1987649124) TRANSACTION CODES,

2) Import them and then retype them again in a format you can read, knowing that the next time you import will be exactly the same, or

3) Download the transactions and edit the raw data before importing into Gnucash.

The only "quick" option is #1, unfortunately.

Since Derek pointed out that the Quickfill database cannot discriminate the imported transactions from edited ones, it would seem the only possible solution is to have these transactions altered before they are committed into the register. That's basically what #3 achieves. But I wonder if there wouldn't be a way to get matching routine of the importer to set the description at the same time it sets the destination account? That way, the Quickfill wouldn't even get the incoming description in the first place.

David

--- On Fri, 9/11/09, Elizabeth Dodd <edodd at billiau.net> wrote:

> From: Elizabeth Dodd <edodd at billiau.net>
> Subject: Re: Quickfill Issues
> To: gnucash-user at gnucash.org
> Date: Friday, September 11, 2009, 12:33 AM
> On Fri, 11 Sep 2009, Colin Law
> wrote:
> > 2009/9/10 Wayne Bird <wrbird at hotmail.com>:
> > > Hello Colin,
> > >
> > >> Where are you importing the data from?
> > >
> > > I'm importing the data from my financial
> institution.
> >
> > Can you save it and edit it before you import it?
> > Alternatively ask them to stop using all upper
> case.  I suppose the
> > latter is a foolish suggestion on my part.
> >
> > Colin
> 
> 
> Anything I import comes in capital letters.
> I always use lower case 
> Eventually I decided that it wasn't worth the trouble to
> change so now I 
> ignore the 'untidiness'.
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> 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.
>