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

            Bug ID: 352789
           Summary: Investment CSV import case sensitivity
           Product: kmymoney4
           Version: 4.7.2
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: csvimporter
          Assignee: kmymoney-devel@kde.org
          Reporter: k...@picodesign.de

When importing a CSV that contains trades, the symbol matching always converts
the symbols to lowercase. However, the usual convention is uppercase symbols.
(I have AMD in my CSV and get amd, which looks weird).
The full equity names are also converted to lowercase (i.e 'Advanced Micro
Devices Inc' ~> 'advanced micro devices inc'), even though they should
certainly just stay as they are.

Even when I edit the symbol name afterwards to be uppercase, the matching for
existing symbols during CSV import doesn't work. This matching should be
case-insensitive (i.e it doesn't matter whether my CSV contains 'amd' or
'AMD').



Another minor issue: if the amount field contains no decimal separator, the
default separator is automatically appended during import. This leads to
problems when the CSV uses a different separator than the one in KMyMoney by
default.
e.g for Amount "300" and Price "12.50" with , as the default decimal separator
in KMyMoney, I have to change the CSV to have amount "300.00" because otherwise
the import makes it "300,00". 

Reproducible: Always

Steps to Reproduce:
1. File > Import > CSV
2. Choose 'Investment'
3. Step through the process of choosing fields
4. Get to the "Edit equities and symbols" dialog

Actual Results:  
All fields in the symbols column are lowercase.

Expected Results:  
The symbols column keeps whatever case was in the CSV.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel

Reply via email to