Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
The last one is not as bullet proof as the first one.
Personally I like the last one too. But I had respondents which assigned e.g 1 on two dropdowns and didn't get why they couldn't move on. The first ranking example is preventing that two items have the same rank assigned.
The difference betwwen the 1st and last are the "mandatory" set on the 1st one, if yu set mandatory to the last one too : you don't have to control 1 is set if 2 is set (count(self)==max(self)).
And if you disable mandatory on 1st : you need to add count(self)==max(self)
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
Hello, I like the first solution, but if I want to build the the array with the previous question like
"((H6_SQ001.NAOK == "Y" or H6_SQ002.NAOK == "Y" or H6_SQ003.NAOK == "Y" or H6_SQ004.NAOK == "Y" or H6_SQ005.NAOK == "Y" or H6_SQ006.NAOK == "Y" or H6_SQ007.NAOK == "Y" or H6_SQ008.NAOK == "Y" or H6_other.NAOK == "Y"))"
and filtering the array with question H6
Then the "unique(self)" validation does not work any more.
Do you have an idea?
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.