I am using the question type described in the manual as "Array (flexible labels) dual scale (dropdown list layout)". Here's a (fake) example: I want to know about people's music listening preferences, so I ask: For each composer whose music you listen to, indicate primary type of music you listen to, and then rate it. My sub-questions are composers; Beethoven, Schubert, Bartok. My first set of dropdown lists are types of compositions; sonatas, songs, symphonies. My second set of dropdown lists are ratings; love, indifferent, hate. I've used the advanced settings to require a minimum of 1 response, as I only want survey-takers to respond for composers they listen to, and not necessarily for all of them.

If a survey-taker responds, say, Beethoven--sonata--love and makes no other responses, that's fine, and Limesurvey accepts that. That's good. If the survey-taker responds, say, Beethoven--sonata and leaves out the rating, Limesurvey, quite appropriately, prompts the survey-taker to complete the answer. That's good. The problem is, if the survey-taker responds Beethoven--sonata--love AND Schubert--song with no rating, Limesurvey accepts that--that is, as long as there is at least one complete response, Limesurvey doesn't seem to care if there are also partial responses. It's important that I do not allow partial responses, partly because I have a complex set of conditionals following the array, and partly because of the nature of the information I am trying to collect in my survey.

Is there any way to set things up so that, in this type of question, Limesurvey will only accept some number of complete responses with no partial ones?

(I thought of making subsequent questions conditional on every possible legitimate answer, but 1) this is incredibly clumsy and 2) I think that would cause the survey to skip the subsequent questions if there are partial answers.)

Thanks!

The administrator has disabled public write access.

JavaScript is currently disabled.Please enable it for a better experience of Jumi.

Another question about the dual scale array with dropdown lists, though this time it looks like a bug:

Lime includes "Please choose" in each dropdown list. A survey-taker who changes his mind after making a choice can revert to "Please choose"--to continue with my previous example, a survey-taker who meant to respond to Bartok and mistakenly responded to Beethoven can undo his responses. However, if the survey-taker proceeds to the next question (via the Next button) and then returns the the dual scale array (via the Previous button), "Please choose" only reappears in the second column of dropdown lists (the "ratings" in my example) and NOT in the first column of lists ("music types"). Thus, a survey-taker can not go back and correct erroneous responses once he navigates away from the question. As the dual scale array I am using has some 15 sub-questions (with subsequent conditionals), mistakes are easy to make!
Any way around this?

Yes, I thought of putting in a N/A-type option, and have anticipated the complications this could add to the data. What puzzles me, though, and the reason I suspected a bug, is that only the first column of drop-down lists no longer gives the option of reverting to "Please choose" when the survey-taker navigates away from the page and then returns to it, while the second column maintains the "Please choose" option.

COMPLETE SUCCESS!! Tony, thanks so much! As I'd wanted, the array with dual dropdown lists now only accepts sub-questions when responses are chosen in both dropdown lists, and survey-takers can navigate back from subsequent questions and change their dropdown list responses back to PLEASE CHOOSE. As a very big array and lots of subsequent conditional-dependent questions is the crux of our survey, this is just what we needed.

Since we didn't even need to consult someone knowledgeable in JavaScript to incorporate the scripts you provided (I hadn't realized that they could simply be plugged into the question editing box), I'll describe the process we went through, for the benefit of forum members whose level of programming naivety matches my own:
First we googled "limesurvey javascript" to learn how to incorporate the scripts, and found manual.limesurvey.org/Workarounds:_Manip...28eg._JavaScript_etc
Scrolling down to "How to use Script (eg.JavaScript etc.) in LimeSurvey?", we followed the instructions to go to Global setting --> Security and set "Filter HTML for XSS" to "Off"--though the actual choices were, in fact, "yes" or "no", not "off" or "on". So we set it to "no". Then we went to the editing box for the array question, clicked on the "Source" button (the icon looks like a sheet of paper with lines of text), copied and pasted both of Tony's suggested scripts into the box, saved, and tested the survey. That's it.

Now I have a few questions:

1. Out of curiosity, after successfully testing the survey with the inserted scripts, we re-set the Filter HTML for XSS to "on", thinking the scripts might then no longer work. We were wrong--it seemed to make no difference either way. Can you tell me anything about the function of this filter? And what's with the on/off versus yes/no?

2. What's the best way to help out other LimeSurvey users, other than my simple description in this forum post? Should I post these as work-arounds?

3. You agreed that the issue of only one set of dropdown lists allowing a reversion to PLEASE SELECT is indeed a bug. Is it enough that you now know about it, or would it be helpful if I filed a bug report?

4. What about the issue of acceptance of partial responses? Is that considered a bug, or something to for Feature Requests?

1) The XSS filter prevents you from entering a script when using the editor, it does not prevent the script from being rendered. If you turn on the filter and then go back and edit that question, the script will be dropped.

2) Sure, you can add these to the workarounds if you like. It's a wiki so anyone can play.