Skip to Content
Author's profile photo Dwayne Phillips

An approach for fixing delimiter issues in LMS CSV reports using Plateau Report Designer


Currently comma separated values files (CSV) in the Learning Management System (LMS) can cause issues and require additional formatting for countries that do not use a comma as their list separator.  Many countries outside the US use a semicolon (;) as their list separator.  This means that when the CSV is initially interpreted by their version of excel, with the regional settings of their computer, the best case is users have to go through an extra step of doing a text to column with a comma delimiter to use the report.  The worst case is an unusable report because of a character that causes the text to columns to malfunction, which misaligns all the data.  It is the case of the unusable report that led to the research and eventual solution found for this post.

Items Needed for Solution:

  • Access to Export and Import Reports from your LMS instance.
  • Latest version of Plateau Report Designer (PRD) and a basic working knowledge of the program.


Note: You do not need to be an expert at PRD to apply this fix to reports.  There is no SQL involved in the solution.  You not need JDBC access to the database you are fixing since there is no SQL to test.  You will simply be able to import the .ZIP PRD file and run the report to verify the solution works as intended.  If you need some basic information or want to become familiar with the Plateau Report Designer, there is an article here.


Choose the CSV report you want to export from your instance.  We are going to export the Learning History (CSV) for our example. You will navigate to the Learning Admin -> Reports and find the report you want to export.  For the purposes of the example of this solution the Learning History (CSV) report will be used. 


Note: Make sure you have changed the default file name to something new before you open in PRD. This will help prevent your from importing your changes over the standard report in your instance.

If you are familiar with custom reporting I will outline the steps broadly here.  You may not need the more in-depth walk through provided in this section below and you can skip to the examples after reviewing these steps:

  1. Export the report, rename it and load into PRD.
  2. Insert a header row above the first row of labels.
  3. Merge all of the header row into one large box/column.
  4. Insert a label into the new large header box and name it sep=
  5. Save your report and import it as a new custom report for testing.

The first step is covered above with the choice and picture of the Learning History (CSV) report chosen for the example and the export button next to it is highlighted.

Next you will want to open the report in your PRD tool.  Go into the outline view (red 1 below) and click inside a cell so you can see all of the table row selectors appear (red 2 below.)


You are going to select the first rows’ selector to highlight the entire row.  Then you will left click and go down to Insert -> Row -> Above (pictured below.)


This will add a header row above the row you selected.  Make sure it is a header row and not a detail row.  It should look like the following image:/wp-content/uploads/2016/03/prd4_912876.jpg

Next you will want to select the first box of the header row and slide over all the way to the last column of the header row and hold shift and select the last box.  Once this is done the row will be highlighted in blue (Note: This is not the same if you try to use the entire row selector.  You must select the first box and last while holding shift before you click on the last box.)  If you have done the selection correctly you will see a merge option (not grayed out/pictured below) when you right click in the boxes you have highlighted, you want all of these boxes merged into one large box.


Once you have the single header box, right click inside it and go to Insert -> Label.


You then need to enter the name of the label which should be sep=


This is the actual fix to the report.  You now need to save the report, save the zip and import it back into your instance. Please remember to NOT overwrite your existing standard SF reports as a best practice.  If you renamed the file as mentioned above this should not be an issue or option.

Samples and Testing:

To test the regional settings were changed to have the list separator as a semicolon, and then the old learning history report and the updated learning history reports were run to show the difference in the outputs when opened in excel.

If you want to do your own tests to change your settings for list separator go to your windows control panel -> region and language (or regional settings) -> additional settings then change the list separator to ; (These steps may vary depending on your version of operating system)


Original Learning History (CSV) with a semicolon as a delimiter:


Learning History (CSV) Separation Fix applied with semicolon set as delimeter:


With the fix applied the column are automatically set and the sep= header is not shown.  For some versions of excel for Macintosh the sep= may appear, but it does not affect the behavior of the report and can simply be removed.  So far no windows versions of excel seem to display it.


This problem with separators is a known issue that people on the support forums have notified Successfactors (SF) of and requested a fix be applied to the standard SF reports.  It is currently being considered by SF for implementation according the the forums as well as an enhancement request from users.  The solution provided above is something that can be used to bridge this gap until SF implements their own fix.

If you implement this solution and there is an issue I have not covered I would ask that you please leave them it in the comments.  Also, if there is something I did not go into enough detail on, please feel free to comment and I will answer them as quickly as possible.  This solution is written for someone with basic PRD experience, so the howto of importing and exporting the report are not covered in-depth.

I hope to be providing some more PRD reporting samples and howtos for basic issues that arise in the future.  If you have any suggestion for basic/common problems or requests please feel free to comment or contact me.

For convenience you can download the .zip history report via dropbox here.

Thanks for your attention and feedback,
Dwayne Phillips – Veritas Prime

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Very helpful. Thank you.

      Author's profile photo Former Member
      Former Member

      Dear Dwayne

      Thanks for the document.

      We seek your expert help on a unique issue that we are facing with one of the Learning reports.  When we download the report, we have wrap issue in comments field with one specific employee.  While all other employee data shows unwrapped, this employee shows with line breaks.  What is your suggestion for this issue.....Please advice




      Author's profile photo Dwayne Phillips
      Dwayne Phillips
      Blog Post Author

      Since the last update with SF there are now different delimiters you can use.  I would try to use a different delimiter when you run the report and see if Excel can then handle it.  I will put in an image of where the new delimiter selection is:


      Hope that helps,