Question - Configurable Delimiter in CSV-Exports

Hi there,
when exporting Content to CSV files (from filters, Reports or received by email) the delimiter is set to ,
So, this file can then easily Import to Excel for further editing, sorting, reporting, etc.

However on Client Systems not running with the language set to “English” the delimiter might be some other then ,
for example, I’m using a Windows Client with German language Settings. So the default delimiter is set to ;

It would be very nice to make the CSV delimiter configurable on a per user basis.
The delimiter should then be used when exporting data to CSV from the web and for automated email notifications to that user.



The import functionality has been improved and standarized on the new template, we have got a few requests for this:

1- change delimiters
2- accept custom fields on the import fields
3- deal with apostrophes by double quoting every cell

I’ll ask kris to github and put it on the backlog

Thanks Bjoern

I’m not asking for the delimiters on Input here, but on Output.

Try to open a CSV in MS Excel straight from the download on a Windows System configured with a german locale und you will see what I mean.

we will look at this, we can enclose cells in single or double quotes probably, we’ll send you over a file for you to test wiht your excel app once we get to this

this is no Problem on Quotation but on the delimiter itself.
A en-us-System uses the comma as a delimiter: ,
However a de-de-System uses a semicolon as delimiter: ;

I know it sounds weird but this is a “Problem” with Excel since years. Google the web for it and you get thousands of hits.

The best solution (in my opinion) is to have a configureable Setting on a per-user-Basis on what delimiter she wants to use.


1 Like

ohhhh! ok - we never heard anyone with this but now we understand the issue we’ll see what can be done.

On e3.23.0 the Settings / Delimiter setting allows you to define delimiter for exporting filters alone, the idea is we have the same option for importing csv files as well.

By default we will use “,” on both settings.

Test case:

  • set “,” on both options
  • test exporting Third Parties using filter options, we should see “,”
  • download CSV template for importing “Third Party”, the file should use “,”. Complete the file, try importing and it should work
  • set ;" on both options
  • test exporting Third Parties using filter options, we should see “;”
  • download CSV template for importing “Third Party”, the file should use “;”. Complete the file, try importing and it should work


Changing the delimitor from , to ; doesn’t seem to work for at least the “Business Risk”, export All Pages option. Those exports still give me comma’s in column “Internal Control Treatment” when multiple controls are mapped to a risk. I tried ‘reload’ and logging out/in again.

Our control titles typically include a comma per design and as such changing the delimiter to ; would be of great help to us.

Monthy, the -Anon- Director reviews X and resolves Y before sign off
Quarterly, the -Anon- manager authorizes Y…

App Version: 3.23.2 | DB Schema Version: 20240104121424

Hi Anon,

I’m based in Belgium where the default delimeter is also “;” so I am faced with same problem. I have created my workaround as follow:

  • I create my CSV uploads in Excel and the fields where there is a comma’s in the title/description I put them in between double quote’s.
  • Afterwards I do a replace in NotePad ++ of the triple quotes (Excel does this automatically when exporting) to a single ( “”" => "). This fixes the problem of the comma’s in descriptions.
  • A replace of the ; => ,

Then your CSV will work as flawless with comma’s in your titles.

Hope this helps you while waiting for the fix of the delimiter.

I also noticed that the ; does not work correctly with imports even with delimiter set to ;. Currently working with compliance packages and mappings CSV imports.

Thanks Hopla – appreciated. I’m referring to the export files though. I use this export as datasource for more flexibility in our reporting and not able to split delimited cells makes reporting a time consuming task.

You are right. It is working only for the current page.
We should be able to fix it in the 3.24.0 release.

Int. ref.:

The new 3.24.0 release did make using csv-exports somewhat easier by this " ; " fix, however, it’s not fixed consistently.

If you have multiple controls linked to a risk, each control is still seperated by a comma, not a " ; " when doing a csv export from the Business Risk Management module.

can you please give us a step by step on how to reproduce this issue? screenshots are always useful. thank you

Sure - in the Business Risk Management screenshot below you see 1 risk with 2 controls. In the CSV export (see copy paste below as well), the 2 controls are only seperated by a comma, not somethinig like ; or " ". That ; and " " seperation now only seems to be used to distingish between different columns only (i.e. Process, Risk title etc).

“Business Interruption due to cyber-attack (ATC)”;“Annually, the MB approves the IT Risk and Control Assessment prepared by the IT Director, C-CYB-115 Annually, the Risk Manager reviews the SOC audit reports of critical service providers”


What I try to have my report look like is something like this; with each control on its seperate line instead of in 1 cell:


Adding a new line or changing the separator to a delimiter does not sound correct to me, at least not in CSV.
I’m creating an issue so there is a possibility to export excel ready file (xls), but I believe it won’t be happening very soon as all power is now focused on the new user interface. Sorry!

Int. ref.: