Hi,

I just started using KMyMoney and I really like it.
However, I stumbled over a problem with importing CSV data from my Bank.

There seems to be two options - however, both options do not really work without workarounds:

1.) CSV Import:
Problem: Default separator is "Colon" and is not changeable
Workaround: Open in Office and export again with Colon separator

2.) AQBanking Import of CSV
Problem 1: Can not Import files with multi-line Fields (works with tweaked csv import)
Workaround: Open in Office + delete fields (fortunately they are not really necessary)

Problem 2: Some Records are not imported correctly (worked with teaked csv import)
NO Workaround found so far

Anyone has some ideas?
(Most preferable would be a changeable CSV separator)

My Sytem Data:
Linux (Arch)
Qt: 4.8.7
KDE Development Platform: 4.14.17
KMyMoney: 4.7.2
Aqbanking 5.5.1-2

Br,
ML

I tried this in 4.6.4. It worked for me. You are right that the field delimiter cannot be changed, but I think this only happens when KMM knows for sure what the delimiter is. I changed between comma and semicolon and had no problems. If the delimiter is semicolon, KMM detects it but at the same time you can change the corresponding setting. Please verify all settings carefully. You have to set both field and decimal separators right as well as define all fields. I found that the importer detects errors and inconsistencies quite well (date format, inconsistent use of decimal separator, etc. If it still does not work for you, try limiting your CSV file to a single line that fails and publish here so we can help figuring it out.

Hi, Thanks for the hint.

I figured out the problem: It seem if there are too many colons in the file - e.g. in the memo text, etc - KMyMoney thinks this is the separator.
(Regardless if they are in quoted fields or not).

Example:
"Date","Amount","Transactiontext"
"26.02.2016","100","a:b:c:d:e:d:f:g:h:le:e:g:h:er:erer:erer:::::er::::::erer:::::::erer::::::erer"

In my opinion the main error is that you can not change the character.
You depend on the - in this case false - auto detection....

Br,
ML

I don't know the algorithm, but characters included in quotes should not be considered in determining the separator. I agree the user should always have control over the separator. Would you consider filing a bug with these two issues?