When exporting a configuration from a service template, the resulting CSV has semicolons instead of commas to separate columns. Also to note, when importing the same CSV it will fail because the columns are not comma-separated.
In Cube settings under “Regional”, I have tried setting the CSV separator set to “comma” as well as “Windows culture” (I am in the US, where the Windows default is comma), but it still exports with a semicolon.
To note, when exporting elements to CSV, it will follow the CSV separator selected here. The issue only occurs with service template configurations.
Is this a bug? Or can this setting be modified somewhere else?
Thanks!
Hi Nick, I tested this locally on a v10.4 CU10 and v10.5.1 and I can verify the behavior you see.
My regional settings are also defined using a comma, but the CSV is still exported using semi-colons. Even when configuring it via Cube settings, it remains unchanged.
You will have noticed it in your mails already, but I took the liberty to create a task for this and have already sent it to our SW team: Exporting service template CSV not in configured format | Collaboration
Hi Nick,
If this impacts working with service templates, here is a workaround that you can use until a permanent fix becomes available.
You can edit the exported CSV file and at the top of the file type in
sep=;
If you then open the file in Excel, it will use the correct separator to interpret your data.
If your regional settings are set to comma separated, then Excel will save it with the correct separator afterwards.
This will allow you to edit the exported file and use it for import.