https://bugs.kde.org/show_bug.cgi?id=437810
Bug ID: 437810
Summary: CSV importer should trim the column contents before
importing
Product: kmymoney
Version: 5.1.1
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: importer
Assignee: kmymoney-de...@kde.org
Reporter: m...@dawidwrobel.com
Target Milestone: ---
SUMMARY
When importing my brokerage account's transaction history, I did not notice
that the SYMBOL column contents were prefixed with a whitespace. When importing
such file, the importer correctly (i.e. sans prepending whitespace) created all
of the previously missing securities. However, after continuing with the
importing of actual transactions, it failed to match the non-trimmed symbol
with the previously created trimmed securities.
STEPS TO REPRODUCE
1. Attempt to import a CSV with symbols having a space in front of them
OBSERVED RESULT
The securities are created as expected with the space trimmed, but the import
itself fails with "This imported statement contains investment transactions
with no security. These transactions will be ignored."
EXPECTED RESULT
The whitespace should be trimmed from all of the cells and the transactions
should import properly
--
You are receiving this mail because:
You are watching all bug changes.
