KMyMoney Vers.: 4.6.4 Import CSV with ";" Separator OK Vers.: 4.7.2 Import CSV only ","-Sparator akzepted. Try to change, but it does not work. Mit freundlichen Grüßen siegfried Reproducible: Always Steps to Reproduce: 1.Datei/Import/CSV 2.CSV-Assistent: 1. Start (Bank, select File) 2.Trennzeichen Feldtrennzeichen: Komma(,) Dropdownlist select Semikolon(;) but it will not take it, its still Komma(,) shown. And it das work with Komma - I need a Semmikolon. 3.In Vers.: 4.6.4 its OK - I can use a Semikolon Actual Results: its still Komma (,) Expected Results: take the change from dropdownlist to Semikolon (;) I use Win10 prof. 64bit My workaround: I change all ";" to "," in MS-Excel - takes o lot off time So I use Vers 4.6.4
Originally, the user needed to select the appropriate data separator, but for some while now the CSV plugin detects the one actually used in the file, so it is not possible for the user to make a selection manually. So, when you open your CSV file, the importer should display the data correctly formatted into individual fields. In your workaround, you say "...: I change all ";" to "," in MS-Excel ...", so it sounds as though your data must be incorrectly formatted/displayed when first loaded. So I am absolutely clear on this, would you please confirm that this is so. The importer works correctly here with ';' separators. This is on Linux, so it appears there may be a problem under Windows. Unfortunately I am not able to run Windows, so it would be useful if another user on Windows can test this.
Vers::4.7.2: Yes, my data are incorrectly formatted/displayed when first loaded. Now I use Vers.: 4.6.4 I can change the separator to ";" and all works fine
(In reply to Siegfried Wohlgemuth from comment #2) > Vers::4.7.2: Yes, my data are incorrectly formatted/displayed when first > loaded. > Now I use Vers.: 4.6.4 I can change the separator to ";" and all works fine OK, now, just to be certain, when you switched from 4.6.4 to 4.7.2, are you sure you completely uninstalled absolutely everything from the 4.6.4 installation? Strange things can happen otherwise.
Created attachment 95501 [details] attachment-23489-0.html I have installed a new PC (Win7 CD-installation, updated Win7, upgrade to Win10, and first I installed Kmymoney Vers.: 4.7.2. but it works not correctly, so I changed to 4.6.2 Without uninstalling Vers 4.7.2 - now I can do my work. 2015-11-11 17:49 GMT+01:00 allan via KDE Bugzilla <bugzilla_noreply@kde.org> : > https://bugs.kde.org/show_bug.cgi?id=355116 > > --- Comment #3 from allan <agander93@gmail.com> --- > (In reply to Siegfried Wohlgemuth from comment #2) > > Vers::4.7.2: Yes, my data are incorrectly formatted/displayed when first > > loaded. > > Now I use Vers.: 4.6.4 I can change the separator to ";" and all works > fine > > OK, now, just to be certain, when you switched from 4.6.4 to 4.7.2, are you > sure you completely uninstalled absolutely everything from the 4.6.4 > installation? Strange things can happen otherwise. > > -- > You are receiving this mail because: > You reported the bug. >
I can confirm this bug on Kubuntu 15.10 with KMyMoney 4.7.2 (continuously upgraded by packet managers of course). The csv-file is displayed if as recognized as separated by comma instead of semicolon. I compared it using the csv-import dialogue of libre office. It's nice to have auto-recognition but I'd like the feature to intervene by the displayed dropdown.
(In reply to Tim from comment #5) > I can confirm this bug on Kubuntu 15.10 with KMyMoney 4.7.2 (continuously > upgraded by packet managers of course). > The csv-file is displayed if as recognized as separated by comma instead of > semicolon. I compared it using the csv-import dialogue of libre office. > > It's nice to have auto-recognition but I'd like the feature to intervene by > the displayed dropdown. I'm going to be out of commission for some days, but will look into this.
I have now installed the stable release 4.7.2 and have been able to correctly import several semi-colon separated files with no problems at all. The files are displayed correctly formatted, and the semi-colon is shown as the separator used. My 4.7.2 has the date 27 Apr 2015, is 913.8Mb (958,167,280 b), 5699 files and 522 sub-folders, although these last two could have been locally added/deleted. If that is not what you have then I suggest you contact your distro, or download and build the stable version. Distros do sometimes make their own changes.
> It's nice to have auto-recognition but I'd like the feature to intervene by > the displayed dropdown. If the automatic recognition is working correctly, this wouldn't help.
So just for the in case anyone is experiencing the same problem: this bug has occurred with 4.7.2-0ubuntu1~ubuntu15.10~ppa3
Created attachment 95641 [details] attachment-17983-0.html I have downloaded it frome heisse.de date: 25.Apr.2015, 311.074.045 Bytes, 14.471 files, 993 folders I use Vers 4.6.4 - I can do all my jobs Thank you for help 2015-11-20 15:11 GMT+01:00 allan via KDE Bugzilla <bugzilla_noreply@kde.org> : > https://bugs.kde.org/show_bug.cgi?id=355116 > > allan <agander93@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|CONFIRMED |RESOLVED > Resolution|--- |WORKSFORME > > --- Comment #7 from allan <agander93@gmail.com> --- > I have now installed the stable release 4.7.2 and have been able to > correctly > import several semi-colon separated files with no problems at all. The > files > are displayed correctly formatted, and the semi-colon is shown as the > separator > used. > > My 4.7.2 has the date 27 Apr 2015, is 913.8Mb (958,167,280 b), 5699 files > and > 522 sub-folders, although these last two could have been locally > added/deleted. > > If that is not what you have then I suggest you contact your distro, or > download and build the stable version. Distros do sometimes make their own > changes. > > -- > You are receiving this mail because: > You reported the bug. >
So the suggested fix is to revert to the older version and call it done?
(In reply to Clark Wierda from comment #11) > So the suggested fix is to revert to the older version and call it done? Linux - > So just for the in case anyone is experiencing the same problem: this bug > has occurred with 4.7.2-0ubuntu1~ubuntu15.10~ppa3 As the official 4.7.2 stable release works correctly, I would go back to Ubuntu, and look for a more up-to-date version of 4.7.2, and preferably the stable release. Windows - I think it would be more sensible to update to 4.7.2. However, it looks like there is a problem there under Windows. I'm expecting a release of 4.8.0 in the fairly near future, which would be the way forward, rather that reverting, although at the moment you may not have a choice.