https://bugs.kde.org/show_bug.cgi?id=340317
--- Comment #6 from allan <agande...@gmail.com> --- (In reply to Ralf Habacker from comment #3) > (In reply to allan from comment #1) > > Just to clarify my thinking, the CSV importer just requires the column > > number for the category. That field is then imported into KMM, as is. > > The importer is unaware of actual category names and IDs.> > > You say that if I would use the following csv line > 1.1.2014;1;-3333.5;"Zinsaufwendungen:2121 Zinsaufwendungen für KFZ > Finanzierung" ; > the related entry will be directly imported into the > category "Expense:Zinsaufwendungen:2121 Zinsaufwendungen für KFZ > Finanzierung" > > but if I use a non present category like > 1.1.2014;1;-3333.5;"2121 Zinsaufwendungen für KFZ Finanzierung" ; > there will be a new category "Expense:2121 Zinsaufwendungen für KFZ > Finanzierung" created. > > > It sounds like you are asking for a search capability in the importer, in > > order to select and import a recognised category, rather than for KMM to > > handle that. Have I got that right? > > I would like to specifiy > 1.1.2014;1;-3333.5;"2121" ; > > and kmm should assign this transaction to the present kmm category > containing the term "2121", which is in the related case > "Expense:Zinsaufwendungen:2121 Zinsaufwendungen für KFZ Finanzierung" This sounds like what you need is a capability for categories which is similar to that for payees, where you can specify alternative category names which will be matched to a base category. Is that it? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
