Bug 358854 - Import CSV or QIF doesn't retain full payee field
Summary: Import CSV or QIF doesn't retain full payee field
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-01 05:47 UTC by Clark Wierda
Modified: 2017-11-11 23:37 UTC (History)
1 user (show)

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


Attachments
attachment-32002-0.html (1.65 KB, text/html)
2016-02-02 04:13 UTC, allan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Clark Wierda 2016-02-01 05:47:04 UTC
Importing from CSV or QIF is getting the last two words of the Payee/Description field.

The text that should be imported is enclosed in "" as specified and the CSV Importer is showing the full text when I use that method.  I have tried without the "", but I get the same result.  I even created a QIF with the correct values, and I still get the same error.

This should show the same value in the Imported Rows as are in the CSV Importer.
This should include all data in the field.
Comment 1 allan 2016-02-01 12:42:42 UTC
I've marked this as 'works for me'.

However, when I imported a file with  four identical payee values, and where there is an existing payee with that (single) name,  just a single payee was imported, not all four.  If I delete that payee, then the import is successful.  If I add all four, again this works.

So, in your case, can you provide  a CSV file which shows the problem, and indicate which, if any of the four intended payee constituents is already a payee.  It may be you need to adjust the matching for that/those payee/s.
Comment 2 Clark Wierda 2016-02-02 03:20:56 UTC
I should know better than to submit bugs to KDE projects by now.  I may yet learn.

I feel obligated to report the conditions where it fails.

"FMCC CAFE 60033818 DEARBORN MI" is interpreted as "DEARBORN MI"
"BEST BUY 00004101 DEARBORN MI" is also interpreted as "DEARBORN MI"

There are others, but you clearly aren't interested since it works for you.
Comment 3 allan 2016-02-02 04:13:40 UTC
Created attachment 96971 [details]
attachment-32002-0.html

Come on now! We're a bit tetchy aren't we?  I don't think you can have read .my response fully as I am interested.If I gave that impression then I must be more careful.While I did mark it as 'works for me' I went on to indicate a possible cause. I also asked one or two questions to help investigate further.There is an issue there but I need more information from you.So pleawe go back and re-read. With your assistance I might be able fto investigate. Allan


Sent from my Samsung device

-------- Original message --------
From: Clark Wierda via KDE Bugzilla <bugzilla_noreply@kde.org> 
Date: 02/02/2016  03:20  (GMT+00:00) 
To: agander93@gmail.com 
Subject: [kmymoney] [Bug 358854] Import CSV or QIF doesn't retain full payee
  field 

https://bugs.kde.org/show_bug.cgi?id=358854

--- Comment #2 from Clark Wierda <cbwierda@gmail.com> ---
I should know better than to submit bugs to KDE projects by now.  I may yet
learn.

I feel obligated to report the conditions where it fails.

"FMCC CAFE 60033818 DEARBORN MI" is interpreted as "DEARBORN MI"
"BEST BUY 00004101 DEARBORN MI" is also interpreted as "DEARBORN MI"

There are others, but you clearly aren't interested since it works for you.
Comment 4 allan 2016-02-04 13:00:04 UTC
(In reply to Clark Wierda from comment #2)
<snip>
> "FMCC CAFE 60033818 DEARBORN MI" is interpreted as "DEARBORN MI"
> "BEST BUY 00004101 DEARBORN MI" is also interpreted as "DEARBORN MI"

This looks like a payee 'DEARBORN MI' is set up as a simple match, so, when it is encountered, it is treated as the complete payee name, and the remaining data is dropped.

The OP would need to edit matching to enlarge that payee to include whatever data is required.