In my user (myself) settings the delimiter in advanced tabs was still ‘,’ so I changed it and it finally work ! Its look like the delimiter in user setting override the one in the general settings.
Next issue : the UTF-8 encode.
If I edit my exported CSV in notepad here is whats I have :
Unfortunately these CSV issues are tough to get right, Microsoft made some terrible options here and they are almost impossible to deal with without some extra steps.
I use Notepad++ and always open my CSV exports first there, and I check encoding and change it (their “Encoding” menu is great for this) before opening in Excel.
The fact is that not all user will have the time to edit it in a notpad, to re change every € symbol … I need to find a fix at the source of the problem for my user (so it will be transparent for them.)
Another thing that occurred to me is that in Excel, instead of double-clicking the CSV to open it, just start a blank spreadsheet and use the Text Import Wizard:
I dont have AINSI in suitecrm option. Got a lot of ISO-8859 but that dont work too…
The import data thing work. But thats not really good for the workflow… I will have to send the .csv to client/provider… :unsure:
The really strange thing is that in UTF16-LE, if I open it with a notepad, everthing is normal, the “€” char display well, and when I open it with excel I got a weird “¬” instead of “€”.
EDIT : Also tried to make a new currencie (even if I already got an EURO one…) Changed nothing.
You have to work with what you have. As I said, Microsoft’s handling of this is not consistent (it makes assumptions based on the computer’s language, instead of just relying on the actual text file).
So SuiteCRM is producing the text file with the encoding you specify, it can’t do any better.
Now you must come up with your process, it could be an Excel macro to automate some steps. Make sure you test this in computers with different Locales, especially if you have international clients.