GC 2.6.12 QIF Import Comments

[redrupj at o2.co.uk]

I can appreciate QIF Import has other uses where dupilcate matching is 
appropriate atlthough with the limited identfification fields program 
displays I dont see how user can do selection accurately.

For migration purposes (my case) the checkboxes sound gound ;-)

I realise code is volunteer baesd and development time has to be 
prioritised. I would say however that in my experience it is crucial any 
software migration process needs to be made as smooth/painless/easy... 
as possible .. if not that potential new user/customer just gives 
up/goes elsewhere.

John


On 06/07/2016 11:49, R. Victor Klassen wrote:
> On Jul 5, 2016, at 7:16 PM, Listsub <listsub at liberator-systems.co.uk> wrote:
>
>> Further it is not clear why GC even needs to do any matching when a complete logical set of data is being imported which contains no ambiguous data?
>>
>> John
> QIF import is for far more than transferring files from Quicken (or another software system) to GnuCash.  In particular the most common case would be pulling in data from a financial institution that happens to support QIF export.  In this case the user may have entered any subset of the transactions over the course of the month and then when the month end comes, pull in the entire set, some of which need to be matched as duplicates.  Perhaps you were hoping for a checkbox that says “trust me, there aren’t any duplicates”?
>
> For that matter I’d like checkboxes that say the date format is the same as last time, and “I’ve imported from this source before, don’t ask me so many questions along the way”.  But that’s all a matter of time and priorities, as this code base is developed and maintained by volunteers.
> _______________________________________________
> 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.
>
>