| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20020 | Bug reports | Import/Export | public | 2025-03-19 09:21 | 2025-05-12 08:23 |
| Reporter | SueStL | Assigned To | gabrieljenik | ||
| Priority | none | Severity | partial_block | ||
| Status | assigned | Resolution | open | ||
| Product Version | 6.5.x | ||||
| Summary | 20020: SPSS export - multiple answers question | ||||
| Description | We have been using “Export answers to SPSS” to export data for many years. After upgrading to version 6.5, we now have a problem with this type of export. When exporting to SPSS (via “.sps” and “.dat” file), multiple answer questions are actually automatically recoded into 1=“selected”, 0=“not selected” and empty fields “” become SYSMIS - unfortunately, this automatic recoding no longer happens with us. Only the “1” is exported for selected answer options; the 0 becomes the SYSMIS. I have already asked in the forum. the error could already be reproduced with version 6.10.5. There the data file is not filled correctly. The xls-export shows that the data is available with “0” and “1” and “”). Only the spss export (via “.sps” and “.dat” file) causes problems. | ||||
| Steps To Reproduce | Export to SPSS (via “.sps” and “.dat” file) | ||||
| Tags | export, spss | ||||
| Bug heat | 4 | ||||
| Complete LimeSurvey version number (& build) | Version 6.5.17+240715 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | |||||
| Database type & version | don´t know yet - i will add asap | ||||
| Server OS (if known) | |||||
| Webserver software & version (if known) | |||||
| PHP Version | don´t know yet - i will add asap | ||||
 |
Betriebssystem: Ubuntu (Linux) 22.04.4 LTS |
 |
Can you please provide an lsa file we can use to reproduce the issue?
From which version? Thanks |
|
|
Thanks for the information. I am sorry, what I wasn't able to reproduce is the original behaviour you described.
Do you recall a version when this was actually happening? |
|
|
So you were having the expected behaviour on 3.23.1+200825 , right? |
|
|
Exactly! Before the update (in version 3.23.1+200825) “1”, “0” and "" SYSMIS were used for coding. In version 6.5.17 there is only “1” and “” SYSMIS (with the exception of the Excel export. The data is still coded with “1”, “0” and SYSMIS via Excel) |
