Bug 396758 - CSV: creates bogus payee´s with csv file with combines payee/description field
Summary: CSV: creates bogus payee´s with csv file with combines payee/description field
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.0.1
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-22 16:43 UTC by Martin Steigerwald
Modified: 2022-12-29 05:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
privacy-edited csv file, saved as UTF-8 by Libreoffice, was ISO-8859-15 or so (709 bytes, text/csv)
2018-07-22 16:43 UTC, Martin Steigerwald
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2018-07-22 16:43:07 UTC
Created attachment 114067 [details]
privacy-edited csv file, saved as UTF-8 by Libreoffice, was ISO-8859-15 or so

I have no idea what to do about it, but when having a file that uses a description file either for description the type of transaction or the recipient, for any lines that describe the type of transaction KMyMoney adds a payee.

For example I attach a privacy-edited file for a debit card.

There are description fields like "compensation debit card according to invoice from some date". KMyMoney adds a payee for each of them. In case of the description with a date or another information that changes these add up.

Probably it would be easier to be able to leave out the description/payee field altogether and stuff it all into memo. Then I can just go through the entries myself and add the right payee with autocomplete.

Another option would be a way to auto clean up payees without any transactions.

Even better would be a standard CSV format for all banks and debit cards with one field for payee and one for description… but well… that would be up to the banks, so KMyMoney has to work with what it receives.

Related to: 393441 - CSV import: description field original text not saved permanently
Comment 1 Justin Zobel 2022-11-29 05:06:22 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-14 05:13:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-29 05:24:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!