nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem adding a replicant - FormAPI related

Adam Stoller

Environment:

I'm running into a problem all of a sudden and am hoping someone here can spot what I'm missing.

DCT Code:

FormAPI (article.js) Code:

Alerts Seen

IN
tmp: [IWItem radio /Article Seciton[2]/Page Break Indicator]
tmp value: 1
Problems with this Web page ...Line: 423
Char: 26
Error: 'null' is null or not an object
Code: 0
URL: http://..../iw-cc/command/iw.formspub.userscript?vpath=//.../default/main/.../datacapture.cfg

I can't figure out why this is failing on the setValue() line.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

I believe it's because you're trying to set a radio button. I've tried to do this before and from what I remember, you need to use standard Javascript statements like ".checked = true" or something similar in order to set the value of the field. The item, itself, is actually an array of all of the field's radio buttons, I believe. setValue() does not work in cases of checkboxes and radio buttons.

At least, this is what I remember. I know the documentation states otherwise... I'll try to find an example of this and repost if/when I find it.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

jbonifaci

Yeah, exactly what dave said. I ended up writing a generic setValue function that I use on all of my items:

//////////////////////////////////////////////////////////////////////
// Function: setValue
// Description: Sets the value of this item. Note that you can set
//              the value of an item that is currently read-only, but
//              you must redraw the form to change the display.
// Parameters:
//     itemObject - Any IWItem object of type browser, checkbox,
//                  hidden, radio, select, text or textarea.
//     value      - For text, textarea, browser, and hidden items,
//                  value is a string representing the new value.
//                  For single select and radio button items, value
//                  is the number of the (zero-based) index of the
//                  option to select.  For multiple select and
//                  checkbox items, value is an array of numbers of
//                  the (zero-based) indices of the options to select.
//
// Return value: boolean indicating success or failure
//////////////////////////////////////////////////////////////////////
function setValue(itemObject, value)
{
    var itemType = itemObject.getType();

    if (itemType.match(/^text(area)?|browser|hidden$/))
    {
        itemObject.setValue(value);
    }
    else if (itemType.match(/^checkbox|radio|select$/))
    {
        var optionsArray = itemObject.getOptions();

        for (var i=0; i<optionsArray.length; i++)
        {
            optionsArray[i].selected = false;
        }

        if (value.length == undefined)
        {
            optionsArray[value].selected = true;
        }
        else
        {
            for (var i=0; i<value.length; i++)
            {
                optionsArray[value[i]].selected = true;
            }
        }

        itemObject.setOptions(optionsArray);
    }
    else
    {
        return false;
    }

    return true;
}

You should be able to use this in your example like this:

setValue(tmp, 0);

~Jeff

Adam Stoller

This looks promising - and I'll probably try using it shortly (got tied up with another problem ...)

Can you explain this line though:

optionsArray[i].selected = false;

if i = 1, then thats:

optionsArray[[1][/1]1].selected = false;

Which looks like very strange syntax to me.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I think he was going for DevNet markup there. He's right with the array stuff, though. This is what I've noticed previously -- wouldn't it be great if the documentation were accurate??

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

jbonifaci

Haha, yeah, I did html and markup instead of just html and was trying to get rid of my italics, oops,

. It should just be [i].

Migrateduser

Dude, that's funny... now the "correction" isn't even visible

Maybe you should quit while you're ahead! Fish is smart!

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

jbonifaci

Hah, got it now, I just bolded my i's,

Adam Stoller

Thanks for the editing job - it makes it a lot easier to understand ... (I think they should just get rid of "Markup" as it breaks so many posts - the default should be "Without HTML" with a single option of "With HTML")

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jbonifaci

What's really annoying is, when I previewed my post with the [i], it showed up as , yet after I posted, it showed up as [i] again. What good is a preview if it doesn't work the same? .

Adam Stoller

Are you sure about: if (value.length == undefined)
I tried using your code and now I get the following in the error message:

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

== is be for numeric values only and I think it should be 'null' rather than 'undefined'. I also think it would always **** out if you're scoping an IF or any other statement on something that's undefined.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

Adam Stoller

So - I'm still confued - what should that line be?

What's even weirder - and perhaps points to some thing else as the culprit - I changed it from '== undefined' to '== null' and edited my DCR again - and I *still* get an error message about 'undefined' is null or not an object.

I just grep'ed through the FormAPI code I have and there's no 'undefined' anywhere in there ???

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I'm actually confused as to why that little block is there anyway. If you're passing 'value' in to the function, why/how would it be undefined? What happens if you were to comment out those few lines?

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

jbonifaci

Adam,

I made a mistake in my post, you need to pass it an int, not a string. So you need:

setValue(tmp, 0);

~Jeff

Btw, original post corrected as well.

jbonifaci

Dave,

It is checking if .length is undefined. You can pass in a single integer or an array of integers.

Jeff

Adam Stoller

Even with those lines commented out - I'm still getting the same error message --- this is rather perplexing. Beyond just trying to get my initial problem resolved - I'm now getting an error message that seems to reference code that doesn't exist!

Okay - I commented out the entire section of code:// if (value.length == null) {
// optionsArray[value].selected = true;
// }
// else {
// for (var i=0; i].selected = true;
// }
// } and that seems to have fixed both this new problem and the original problem.

Thanks!

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jbonifaci

Adam,

As I stated in my previous post, if you use my original code, but pass an integer rather than a string, it will work perfectly.

Jeff

Adam Stoller

Right you are!
I uncommented those lines and changed my calls to pass in 0 instead of "0" - and it does work.

Thanks again!

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jbonifaci

No problem, glad I could help Adam.

cliffhanger

I am currently on TeamSite6.1 and radioButtonITem.setValue() is working fine for me, but it expects an integer not a string.

cliffhanger

I believe. setValue() does not work in cases of checkboxes and radio buttons.

checkBoxItem.setValue() expects an array of zero-based indices. In my template I have a FormAPI entry: checkBoxItem.setValue([0]) and it works just fine.

jbonifaci

If so, I guess I wrote that function for nothing,

. I've wasted 15 minutes of my life doing much more idiotic things than that before though, so I don't feel too bad... Smiley Wink

.

I wonder if the problem I had with items of type radio and checkbox was fixed in a SP, or if I was just on crack the whole time?

Adam Stoller

Well - I tried using: IWDatacapture.getItem(item.getName() + "/Page Break Indicator").setValue(0);but I got an error message about null something or other - so I changed it back to use jbinifaci's code: setValue(IWDatacapture.getItem(item.getName() + "/Page Break Indicator"), 0);and it went back to working - so I guess I'll leave it like that for the time being.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

cliffhanger

Adam,

I don't know whether it's wise to waste more time on this minor thing when you have something working already, but perhaps you could try the following to see if the problem is with setting value to a radio button or with something else:

var radioItem = IWDatacapture.getItem(item.getName() + "/Page Break Indicator");

alert(radioItem.getName()); //just to make sure that radioItem is not null

radioItem.setValue(0);