queXF

Multiple choice answers not imported to limesurvey

Asked by tgoeg

Hi Adam!

I have verified questionnaires with multiple checkboxes and when I output as CSV directly in the quexf webGUI I can see a "Y" for whenever a multiple choice checkbox has been checked. So everything up to here seems to work.

However, if I now import the results to limesurvey, all answers get correctly imported but the multiple choice answers remain NULL.

Is this a known issue? Am I doing something wrong? Can I generate some debug logs to aid in tracking down the root cause? Do you need actual data and if, which table(s) should I dump?

Thanks a lot in advance!
th

Question information

Language:
English Edit question
Status:
Solved
For:
queXF Edit question
Assignee:
No assignee Edit question
Solved by:
Adam Zammit
Solved:
Last query:
Last reply:
Revision history for this message
Adam Zammit (adamzammit) said : 		#1

Hi ,

Apologies for the delay in replying - I hope you have made some progress without me.

Otherwise please look at functions/functions.output.php and the function "uploadrpcJson"

On line approx 124 and 142 there are some commented out var_dump statements that may assist debugging. You could compare the output here and see if the generated variable names match up with what LimeSurvey expects.

If they don't match up - let me know how and we can adjust the code.

Good luck,
Adam

Revision history for this message
tgoeg (tgoeg) said : 		#2

Hello!

Thanks for the pointers.
It seems it is not a problem of matching up the variables. In fact queXF does not even try to export values of multiple choice questions.

I've removed the comments at the var_dump stanzas and got the following for a multiple choice question H1:

["H1"]=> string(17) "181107X2585X19637" (and nothing more)

This is the correct ID, however in queXF's direct CSV output, this question has H1_A5 checked ("Y" in the CSV).
It seems answers to multiple choice questions do not get handled at all.

Has this already worked, i.e. can this be a regression?

Revision history for this message
Best Adam Zammit (adamzammit) said : 		#3

Thanks for the report - I've fixed this now - you can see the updated code for functions.output.php here:

https://bazaar.launchpad.net/~adamzammit/quexf/main/revision/371

Revision history for this message
tgoeg (tgoeg) said : 		#4

I can confirm this fixes it!

Thanks a lot!

Revision history for this message
tgoeg (tgoeg) said : 		#5

Thanks Adam Zammit, that solved my question.

Revision history for this message
tgoeg (tgoeg) said : 		#6

I am getting a timeout when trying to post this at the bug as well, just so you know I wanted to be a good boy ;-)