LS Version: 6.0.1+230411
Own server

Hello everyone. 
We have been using all of the array questions types with radio buttons as the options and have been able to succesfully check one of the radio buttons to a default value using an equation type question and the basic EM code that we all use (if blank then select a value else use the value that is selected). This is all good. 

The issue: When using the same code that works for all of the array type questions in the basic "ARRAY" type, it does not work. it never selects a default value. 

Before sending any of the EM code through, let me just show you a screen shot of the question of type "ARRAY"   
 


this is the type of ARRAY that is NOT working
 
 

DUAL ARRAY for example IS WORKING. 

We have tried various syntax, placing the EQ question with the EM code before and after the question it is referencing, etc, etc, etc. No luck. Before we send additional info, is there any known issues with this scenario (ARRAY QUESTION TYPE with RADIO buttons and being able to set a value via EM code)? 

Thank for any help. 

I would think the ExpressionScript should look something like this:


Can you attach a small sample survey (.lss file) containing only the relevant questions and your ExpressionScript code.

Hi Tony, you are correct. That is the precise syntax with which we began and what has worked for other array types or even for simple multiple choice types using radio groups. It does not however work for the basic array type F question type. By "not work" we mean that when we load the page, our EM code does not select the answer we are instructing. We do not see any of the radio buttons checked in the display and in the code we do not see any checked properties. We do see both when using other array types though. It is just type F arrays that seem to be misbehaving. Reminder: We placed the EM code above and below the question and we have also tried other forms of syntax. We will attempt to attach an edited down version of the test survey in LSS format here. Thanks for your help. 

I can confirm the problem, it is a bug in version 6.x (works as expected in 5.x).

Please file a bug report - bugs.limesurvey.org/bug_report_page.php .

Include your test survey and give a link to the bug here.

Thanks for confirming Tony. I will try to file the bug report but we tried two weeks back and there was an issue that didn't allow us even though we were the official email associated with the account and it also wouldnt allow us to do it anonymously. We'll give it a try though. Thanks

Hi Tony, we tried to access the bug tracker but it continues to not allow us the access we used to have. If you were interested, you are welcome to post the bug. To help save you time you can use the LSS file previously attached in this thread and below this text, I will copy/paste the text I would've used for the bug tracker. Thank you for any help you can give.

BEGIN TEXT**********

Version of Limesurvey: 6.0.1+230411
Server License Type: Our own server

Description of bug:
When we make a question using the ARRAY type (type F) with radio buttons, we can not use EM code to set one of the answers manually.

We can do this with any other type of array question and also with multiple choice type questions that use radio buttons.

We have attempted using the standard syntax and tried many alternatives. We have also tried with the EQ question's EM code placed before or after the array (type f) question.

When the page loads, the radio button is never checked (by visible inspection with the eye and in the code under the properties of the input)

This was posted here:
forums.limesurvey.org/index.php/forum/ca...checked-value#242749

And Tony Partner confirmed that it is a bug and suggested that we post this to the bug tracker.

The sample LSS file is included with this text and can be used to replicate the issue in v6. Tony noted that it is not an issue when tested in v5.

Thanks

Send a simple lss showing the issue please

If you were interested, you are welcome to post the bug.

Done - bugs.limesurvey.org/view.php?id=18785

@DenisChenu, a .lss was provided above and I have attached one to the bug.

We need to get this bug tracker login issue fixed...

I asked Carsten the other day and he said they are on it. We'll see.

tpartner wrote:

@DenisChenu, a .lss was provided above and I have attached one to the bug.
 

Yes : ) Sorry, see it after