Actions

Problems & solutions: Difference between revisions

From LimeSurvey Manual

mNo edit summary
mNo edit summary
Line 3: Line 3:


{{Alert|Under construction}}
{{Alert|Under construction}}
__TOC__
{{Note|In the case in which the solutions are not working or you found other workarounds to some common [[Export responses|export-]] and [[Import responses|import-related problems]], please edit the following wiki. Sharing is caring!}}


=Problems & Solutions= <!--T:161-->
=Problems & Solutions= <!--T:161-->

Revision as of 18:02, 15 February 2019

  Under construction



In the case in which the solutions are not working or you found other workarounds to some common export- and import-related problems, please edit the following wiki. Sharing is caring!


Problems & Solutions

Excel

Modifying responses in Excel prior to Import

In order to make multiple changes to responses, you may choose to Export and open a file in Excel. Make changes to the data (other than the top lines) and then save as a .txt file. If you save as .csv, Excel uses comma-delimits which will not import into LimeSurvey. By saving as a .txt file, Excel saves as a tab-delimited file which imports back into LimeSurvey.


Edit .csv with Excel

In general we do not recommend to use Excel to edit the exported .csv files because Excel does some changes to the internal data structure which results in a failing import. If you nevertheless want to use Excel you have to set the seperator for Excel to a comma in System Control (Windows Systems):

System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,


Workaround to edit .csv files with Excel

Using Excel for editing questions can prevent you from being able to re-import them. But editing is the way to go if you have more than 5 or so options or ranking options, want to use Excel capabilities like sorting, etc.

This is a partial workaround that seems to work in 1.82-essentially, only use Excel on the part of the file that is the data:

  • Export a question similar to what you would like to reuse as .csv file
  • Open the CSV file in a rawtext editor
  • Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.
  • Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish
  • Save the file as Excel CSV, which will likely have no quotes.
  • Open this file in the editor, and Select All, Copy
  • Go back to the file you opened with the rawtext editor
  • Paste over the answers there
  • Save AS, with a different name, maybe one that you can remember for reuse
  • Import this file.


Excel - export limited to 255 columns

Due to limitations in Excel (versions lower and equal to 2003), LimeSurvey can export only 255 columns at the same time. Microsoft has proposed a workaround as a VB macro.

Although newer spreadsheets (Excel >= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can't export more than 255 columns.

Two workarounds are however possible, use one of the following solutions:

  • Either export to CSV and import in your spreadsheet
  • Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results


Excel/.csv - export fails

If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.


CSV

CSV defaults to 255 columns

When exporting large surveys the GUI by default limits the export to the first 255 columns. To work around this, simply mark all data sets for export.


SPSS export

Possible error messages in SPSS

ERROR. command name:Get Data

If you receive the error message ERROR. command name:Get Data. 2267 Unexpected Token missing. please edit the forth line of your syntax file so it points to the absolute path of the data file like

C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat


Error: "Text value unmappable in the current server locale"

This error can happen if you try to open an exported syntax file in SPSS 16. The solution is to force SPSS to interpret the syntax file as unicode.

Open SPSS. Go to Edit > Options > Character encoding for data and syntax. Change the option to "unicode".

LimeSurvey data can now be exported to SPSS 16 without any problem.


Define the scale to use for your variable

It is possible to override the default scale used for a variable by setting the question attribute scale_export to the appropriate value.


Other problems and solutions

Copying responses into a different survey (using tokens)

  1. Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.
  2. Export the responses from the old survey, including tokens, open in Excel.
  3. Use this data to create an Excel worksheet for the standard token file import (eg. Firstname, Lastname, Token, Email address, Email status (OK), Language (En)). Save as .csv and import tokens to the new survey in LimeSurvey.
  4. In Excel, copy the response fields from the old survey responses that you want in the new survey (including token) into the appropriate Excel column of the new survey format.
  5. Save as .txt file.
  6. Use VVImport to import the new data into the new survey.
  7. Possible import errors include date format - some system date fields do not allow a NULL value, some do. If the date looks okay but gives an error, use the Excel cell format "2009-12-01".