Bug 424544 - CSV importer cannot deal with recipient & description in separate(!) columns?
Summary: CSV importer cannot deal with recipient & description in separate(!) columns?
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.0.8
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-22 18:03 UTC by Jens
Modified: 2023-01-21 20:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Select payee and memo using the CSV importer (39.37 KB, image/png)
2020-11-14 10:16 UTC, Thomas Baumgart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jens 2020-07-22 18:03:12 UTC
SUMMARY
see $DUBJECT

STEPS TO REPRODUCE
1. Export any CSV from e.g. iFinance which has separate fields for recipient/origin of transfer, and description (where you usually put order number, customer number, etc).
2. Try importing with kMyMoney.
3. Assigning the CSV columns fails because there is only one column for "recipient/description".

OBSERVED RESULT
See #3

EXPECTED RESULT
Please use separate fields for recipient or origin of funds and for the description, during import and in the app itself.


SOFTWARE/OS VERSIONS: KDE Neon 18.04 with KDE 5.14 and kMyMoney 5.0.8.
Comment 1 Jack 2020-07-22 19:41:35 UTC
Is this a translation issue?  I would interpret what you call recipient as Payee, and description as Memo.  In the CSV import, the Memo field can be taken from multiple columns, and the column used for the Payee can also be part of the Memo column.  If this doesn't help, please expand on your description of the problem with a more detailed example.
Comment 2 Bug Janitor Service 2020-08-06 04:33:11 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 2020-08-21 04:33:12 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!
Comment 4 Jens 2020-11-14 09:39:22 UTC
Hello,
this bug has not been resolved. The finance software from which I am trying to import 14 years of family finances spread over 8 accounts has the following transaction properties:

Usually provided by the bank (FinTS or CSV):
1. Date
2. Payee (eg. "John Doe" or "LIDL SAGT DANKE")
3. Description (e.g. "Dinner" or "LASTSCHRIFT EINZUG EC xxxxx Ref XYYYYY ...")
4. Amount

Usually added manually:
5. Category, hierarchy separated by colons (e.g. "Finances:Bank fees")
6. Comment (e.g. "present for Jane Doe")
7. Tags (e.g. "taxes", "children", etc)

Issues:
- I cannot import #2(payee) and #3(description) separately since this is a single field for kMyMoney called "Payee/Description".
- I cannot import both description and comment because kMyMoney only has a single "Note" field.
- I cannot import tags at all.

Since I have used these features heavily in the past, importing my data into kMyMoney would cause data loss.
But I think adding these properties (and then being able to sort/filter by them, both in the list views but also in reports) would make a lot of sense.

Please consider adding these properties.
I'm willing to help finetune and test; I can create my own builds and debug, I'm just not fluent enough in C++ to fork and start by myself.

Thanks!
Comment 5 Thomas Baumgart 2020-11-14 10:16:49 UTC
Created attachment 133324 [details]
Select payee and memo using the CSV importer

This is certainly not true. The attached screenshot shows that the payee information is taken from column 4 while the description/memo is taken from columns 5, 6, 7, 8 and 9.

Having a separate comment field is a complete different story and a wishlist item by itself and not related to this problem.
Comment 6 Jens 2020-11-14 18:30:14 UTC
If you are correct, then I must be missing something. The column assignment only has one row for "payee/description", so you can choose either columns 4 or 5.

In your screenshot, how do I put your source file's 4 and 5 into *different* fields inside kMyMoney?

I want to search by, and filter by, receipient, description and memo/notes *separately* inside kMyMoney.
Comment 7 Jens 2020-11-14 18:38:07 UTC
PS: Please note that I cannot use the "memo" field because this is already occupied by my "Notes" column.
Comment 8 Jack 2020-11-14 19:09:59 UTC
First, the bug was closed automatically, because you did not respond to my question for additional information (Comment #1 22 July) within 45 days.  When the bug is in "Needsinfo/WaitingForInfo" state, and you reply, you need to set the status back to Opened or Reopened, to prevent this from happening.

As Thomas said, wanting a field other than "memo" to store any other combination of input fields or other data should be logged as a separate "wishlist" bug, as it would be a new feature. 

Looking back at your original entry and Comments #4 and #6, what you call "Description" should probably be used for choosing the Category.  Automatic matching of category on importing data could also be a wishlist bug, but I think most users include any such input Description into the Memo.  Also, the only problem with including putting more than one input field into the Memo is that you can't sort separately on the different pieces, but this is how the program is designed, so you may actually have multiple wishlist items, but they are not actual bugs.  It would be reasonable to simply convert this bug into a Wishlist, but if so, you should be pretty specific in what you are asking for.
Comment 9 Bug Janitor Service 2020-11-29 04:33:40 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 10 Bug Janitor Service 2020-12-14 04:34:02 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!