Just wondering if it is possible pipe the 'Other' category from a multiple choice into an array using the arry filter. Ideally I would like to pipe the specified text, but even the broad category of 'Other' would suffice.

Experimenting with javascript and the jsName attribute I have got "<span id='LEMtailor_Q_21_30'>java87887X14X211</span>" instead of 'java87887X14X211'. Should I report it in Bugtracker or I made a mistake?
Cheers

Experimenting with javascript and the jsName attribute I have got "<span id='LEMtailor_Q_21_30'>java87887X14X211</span>" instead of 'java87887X14X211'. Should I report it in Bugtracker or I made a mistake?
Cheers

No, that isn't a bug. That code is how EM supports dynamic substitution on the same page. Perhaps you were testing the demo listed below, selected the Other option, and saw the message asking why you liked {Q1_other} best. The reason it didn't show the fully substituted value is that EM would have had to do recursive substitution within a page, which it can't do. However, if does do recursive substitution between pages, so if you want to use the Other value on a different page, you will see the entered value for Other was you would expect.

Just upgraded to 1.92 and trying to solve this piping problem. I now have the issue that 'Other-specify' is always piped to subsequent array question and it doesn' seem to be a "checkable/selectable" item in the multi-choice question.

I am but a simple man. To me Java is an island in Indonesia..... Therfore if anyone can help me pipe the 'Other-specify' text into the following question (when it is selected!) I would be most appreciative. I have attached a screen capture of the relevant questions.

You can use an answer code "other" for the question 2 "Other" option and an expression to pipe in the value as in the illustration below (where my Q1 code is multiOpt_p1_1). This will make both the filter and the piping work.

Personally, I'd vote to going back to the way 1.91+ worked. I have plenty of surveys where users want to check the other check-box, but do not be forced to specify any details. The changed implementation does not allow that.

The that caused the current behavior was made by Denis about a month ago.

Personally, I'd vote to going back to the way 1.91+ worked. I have plenty of surveys where users want to check the other check-box, but do not be forced to specify any details. The changed implementation does not allow that.

This would also be my preferred solution as default behavior. Maybe we can then have a second behavior which is triggered by an advanced question setting.

Dear Tony - many thanks for the prompt and detailed help. Worked like a charm. It wasn't immediately obvious what the question code was for my 'other' option but worked it out from the survey logic file.

I encountered the same issue and I tried to use your solution. But the system does not let me use code "other" for Question 2. It gave me a error warning which is "Error: other is a reserved key word". I believe I am using 1.92 version. Any solution for that?