FORMAPI setValue() radio/checkbox item

Teamsite 6.1 6.1.0 Build 36267 Interwoven 20040610 Service Pack 1.
Solaris 5.8
Client IE 6.0
Using the following code as stated in the form api reference does not work for a radio button or checkbox.

IWDatacapture.GetItem("radioitem").setValue(0);

This causes a javascript error " Line 1749 Error: formDocument is null or not an object"
Which if you debug points to a Teamsite javascript function.
I can get around this by using getOptions() setOptions() and changing the selected options.
Has any one else experienced this? Or is it a "user" error?

Find more posts tagged with

Comments

Migrateduser

Aren't you missing / in /radioItem? And isn't it IWDatacapture.getItem( whatever )?

Migrateduser

I just reviewed the 6.1 SP1 release notes. It refers to fixing a problem with GetItem not resolving replicant containers very well.

Check out:
https://support.interwoven.com/library/manuals/teamsite/html/610/ts61_sp1_rn/index.html
hth,

lissa

brandon1

Thanks,

My example below was incorrect. But regardless, the issue still stands. We have reported it to support.

brandon1

I know my code in my initial entry was wrong. But after dealing with support they say this is a browser issue based on the fact they only verify TS to a specific service pack level. I need to roll back to a specific version (yeah right) to alleviate the DOM troubles.

Migrateduser

It is ridiculous to require that everyone in your enterprise (or your vendors and other partners if they access your CMS) be on a specific version of IE, have the right JVM configured, have caching disabled, etc. just to use one application, especially when that JVM conflicts with the requirements of other enterprise applications. But you don't have much choice if you want to avoid issues like this. What are you planning to do?

brandon1

There is a way around the issue basically getOptions to set the ones we want selected as well as setOptions on the item. I plan on confirming or denying the validity of the response by rolling back a dev machine and seeing if that issue still resides. I will post my learnings as they come on this issue. I also plan on getting this listed as a defect (because IMO it is!)

brandon1

For anyone who is interested bugcase # 54698.