[Kmymoney-devel] [kmymoney4] [Bug 346810] CSV importer fails to correctly parse values

[allan]

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

allan <agander93 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WORKSFORME
                 CC|                            |agander93 at gmail.com

--- Comment #6 from allan <agander93 at gmail.com> ---
(In reply to bugs from comment #0)
> I've tried this in the latest version of kmymoney on Fedora 21 and then
> downloaded 4.7.2 and compiled it, but experience the same behavior. When
> importing from CSV, the Payment column isn't updated correctly.
> Additionally, the details column sometimes has a 0 in it, but sometimes has
> the correct value.

I have to admit that you have me confused!  Above, you give your version as
4.7.2, but all the screen shots show a very old version of the importer plugin.
When you switch between different versions, it is very import that you
uninstall the previous version, otherwise you will have a bit of a mongrel on
your hands.  I'm not saying that you didn't uninstall, but definitely, you are
not using the current one, but about two versions older.
The latest, 4.7.2, plugin has two separate windows, one for the wizard and one
for the result table.

The next problem is with your data file.  There is a, possibly unwritten,
convention that when dealing with debits and credits, a transaction may have
either one, but not both.  I have only once before met your version, and I
introduced a coping mechanism.  The user is asked whether he wishes to accept
either the zero field or the non-zero field.
I input your data into my 4.7.2 and waded through the interrogation, and the
outcome was correct.  Whilst it works, it can be a bit labour intensive, and it
may be better to edit the file before import.

-- 
You are receiving this mail because:
You are the assignee for the bug.