Bug 325437 - CSV Importer Problems
Summary: CSV Importer Problems
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 4.6.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-09-29 18:47 UTC by Doug
Modified: 2018-10-27 02:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug 2013-09-29 18:47:30 UTC
CSV importer is buggy.

1.  Cuts off payors randomly after "WDRL-POS "  Sometimes it includes the text that follow, sometimes, not, can't see a pattern to it.
2.  The option to import "debit/credit columns" does not work -- in my case the debits are all negative numbers, so maybe that is the reason.
3.   HUGE problem:  when importing investments, only can import one investment at a time.  So if the account has 30 investments, they all come through as the same investment (or an error) and need to redo manually 30 times.
4.  Generally, the functionality does not seem reliable.
5.  I can change data/fields in the importer dialog, but then the changes seem like they are ignored by the importer at least sometimes.

Reproducible: Always

Steps to Reproduce:
1.  Use the CSV importer.
Actual Results:  
1.  Takes a really long time to import data, lots of manual interventions.

Expected Results:  
1.  Should import the data without large manual interventions.
Comment 1 allan 2013-09-29 20:00:12 UTC
On Sun, 29 Sep 2013 18:47:30 +0000
Doug <dougt901-2012@yahoo.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=325437
> 
>             Bug ID: 325437
>            Summary: CSV Importer Problems
>     Classification: Unclassified
>            Product: kmymoney4
>            Version: 4.6.3
>           Platform: unspecified
>                 OS: Linux
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: NOR
>          Component: general
>           Assignee: kmymoney-devel@kde.org
>           Reporter: dougt901-2012@yahoo.com
> 
> CSV importer is buggy.
> 
> 1.  Cuts off payors randomly after "WDRL-POS "  Sometimes it includes
> the text that follow, sometimes, not, can't see a pattern to it.
 I don't understand that at all.
> 2.  The option to import "debit/credit columns" does not work -- in
> my case the debits are all negative numbers, so maybe that is the
> reason. 
So your file actually has columns for both debits and credits, but just
to make sure you understand, the debits have a minus sign as well?  So
that really makes the positive.  There should be no minus signs.  I've
not come across that before, but could certainly check for that.
> 3.HUGE problem: when importing investments, only can
> import one investment at a time.  So if the account has 30
> investments, they all come through as the same investment (or an
> error) and need to redo manually 30 times.
How are the individual investments identified in the file?  For a
multi-investment file, it is necessary to ensure each has a unique
ticker symbol, which can be added during the import process.  It
doesn't need to be a real symbol, unless you wish to do on-line price
updates
> 4.  Generally, the
> functionality does not seem reliable. 
> 5.  I can change data/fields in
> the importer dialog, but then the changes seem like they are ignored
> by the importer at least sometimes.
> 

Again, I don't have such a problem. 

Investment files tend to be formatted according to the whim of the
producer.  I have been able to import from three quite different
sources, and am happy to try to add more. Are you able to send me,
off-line, a small sample file, at least with a few different
investments, and which will demonstrate your issues?  The data does not
need to be your real private date, as long as the format is retained.

Allan

> Reproducible: Always
> 
> Steps to Reproduce:
> 1.  Use the CSV importer.
> Actual Results:  
> 1.  Takes a really long time to import data, lots of manual
> interventions.
> 
> Expected Results:  
> 1.  Should import the data without large manual interventions.
>
Comment 2 Cristian Oneț 2014-07-31 08:34:20 UTC
Doug, could you provide the information Allan requested?
Comment 3 Cristian Oneț 2014-09-12 14:33:27 UTC
Doug provided the necessary info by mail.
Comment 4 allan 2014-09-12 14:53:37 UTC
Cristian has forwarded your email to me.
In the body of the email, you refer to "Here is a demo file for the importer problem, hopefully with sensitive info removed.  This OFX file has three entries, the third item imports.... ", but the bug report is referring to CSV import, and the bug itself does not appear to mention OFX problems.
Is the truncation problem specific to OFX?
Could you check the payees entries, in particular their 'matching' attributes, as it sounds like the matching process may be editing the payee entries.

So far as CSV imports are concerned, I'm afraid your way behind the times with your KMyMoney version.  However, even later versions, up to 4.7, have the same basic CSV plugin that you have.  The development version has an improved capability, so if you are able to compile from source, that will probably help you.  However, if, not, there will be a further release in the near future which also has that new version.

As mentioned earlier, CSV files do tend to differ in their content, and this is particularly so with investments.  Might you be able to provide a sample of your investmet csv file to see if it may present any problems, or particular treatment.  The actual data may be disguised/changed, as long as the format is retained.

Allan
Comment 5 Cristian Oneț 2014-10-29 14:13:15 UTC
Doug, could you try version 4.7.0 since it contains the new CSV importer Allan was referring to.
Comment 6 Andrew Crouthamel 2018-09-25 03:57:00 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 set the bug status 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 7 Andrew Crouthamel 2018-10-27 02:10:57 UTC
Dear Bug Submitter,

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!