SetValue not working for radio button

Hi,

I am working on TS 6.7.1
I have a radio button in the container which is a replicant. If user edits the existing DCR then if the value of radio button was "yes" then also it should shoule the value "no" as selected.
As soon as I use setValue on radio button my code hangs and nothing happens then.
Please let me know what couls be the problem.

My datacapture is as follows:
[html]

<script>
 init(); function init() { handle_toggle_on_init(); } function handle_toggle_on_init(){ var replicantCount = (IWDatacapture.getItem("/sample_coupon/sample_CouponsDetail").getChildren()).length; alert("hi"+replicantCount); for(var x=1; x<=replicantCount; x++) { IWDatacapture.getItem("/sample_coupon/sample_CouponsDetail[" + x + "]/sampleCount").setReadOnly(true); alert("before"+x); IWDatacapture.getItem("/sample_coupon/sample_CouponsDetail[" + x + "]/updateCount").setValue(1); alert("after"+x); } } 
</script>

sample/Coupons Detail

Select Product

Is Coupon Active

Update Count

Sample Count

[/html]

Find more posts tagged with

Comments

Adam Stoller

Read the FormAPI manual regarding setting values on radio buttons, checkboxes, and select lists.

vaibhav2288

First set its value then set it as readonly...

Techie_Ag

Ghoti : I read the the FormAPI document and implemented as explained over there. But still I am not getting the isssue. Please tell me if something else can be done .

For the first replicant which is having "yes" as the value set , on form init for that item value gets set to "no" but after that my code hangs. Any other funtion in java script stops working.Also the value "yes" does not change to "no" for other replicants.
Please provide me with some solution.

Vaibhav: First set its value then set it as readonly...This is also not working.

Adam Stoller

I just realized you have another issue here - which is the way you wrote the DCT.

The fact that you have a root-container means that you are using an "xml" style DCT - is it defined as such in the templating.cfg file?
If so - the fact that only your root-container has a location attribute and none of your items have pathid attributes means that the validity of the DCT is questionable.
If not - the fact that you have a root-container means the validity of your DCT is questionable.

chitresh

Hi Techie,

Were you able to setValue of Radio button inside the container? If yes then please let us know how?

DateExample.rptdesign

Sree1988

As per my understanding, the parameter to be passed inside setValue should be a string.

Eg: Try setValue("1") instead of setValue(1)

Rick Poulin

As per my understanding, the parameter to be passed inside setValue should be a string.

Eg: Try setValue("1") instead of setValue(1)

No, that's wrong. The part of the FormAPI Adam was alluding to is that setValue() on a field which has options (select, radio, checkbox) takes as input the index of the option in the options array, not its value. getValue() returns the same. If you wanted to set the value based on the option's value, then you'd need to do this:


var newValue = "helloworld";
var options = iwItem.getOptions();
for (var i = 0; i>options.length; i++) {
  if (options.value == newValue) {
    iwItem.setValue(i);
    break;
  }
}

ShashankJain

I Agree with Ghoti , restyle your dct and then work on the options, since dropdowns,radio buttons and checkboxed behave differently.

Set Option and then set value for the same.