problem with custom browse button in the edit mode

Hi,

I've used custom browse buttons in my DCT. It is done so that the whenever user decides to include an internal link(means link to some file in the workare), s/he cannot do a manual entry(field has been made readonly) and has no option but to use the browse button to enter the link.

My code works fine whenever the user decides to add a new link ( new instance of the container). But the problem arises in the edit mode. For eg, say the user had eneterd three entry when the form was created first time. Now in the edit mode user decides to change the value for the first link. Now as my check is based on null/not null, the loop runs thrice (because upto third instance, value is not null) and always ends up updating the last value.

Can someone provide some solution to it?DataCapture and the Javascript files are attached herewith.

Thanks in advance
Mav

Find more posts tagged with

Comments

Adam Stoller

You have:

for(var i = 1; i <= 10; i++){
    if(IWDatacapture.getItem("/footer/links["+i+"]/internal") != null){
        var index=i;
    }
}

Try changing it to:

var index = 0;
for (var i = 1; i <= 10; i++) {
    var item = IWDatacapture.getItem("/footer/links["+i+"]/internal");
    if (item != null && item.getValue() != "") {
        index = i;
    }
}

See if that helps any

curiousmaverick

Adam,

Thanks for the quick reply. But I'm afraid this is not working. Here "Internal" is also a container.

The situation is something like this. Say as new form entry the user added 5 instances. Now s'he decides that 3rd instance value needs to be checked. But now since not null is satisfied till 5th iteration, the 5th value gets updated.

So the question is how to identify the particular whose value needs to be changed.

Regards,
Mav

ISCBorisB

My code works fine whenever the user decides to add a new link...

Sorry but that's not possible, not with the code you've provided. There are too many bugs in it to believe that it ever worked.

For example, linkCustomBrowse() is internal to init(), you can not make up your mind of what you are processing, header or footer,
critical 'index' variable is declared in the wrong lexical scope and so on.

All that notwithstanding, none of it is needed in the first place. onCallout Event Handler 'item' parameter is the IWItem object
associated with the callout that generated the event. So, you already have an object that you are so expeditiously looking for.
Btw, it's all documented in FormAPI manual.

curiousmaverick

In case of a replicant container for the event onCallOut, I dont have to specify the exact instance of the item. So R u saying that I should pass the exact instance every time I Call a function on onCallOut?

Regards,
Mav

Adam Stoller

In case of a replicant container for the event onCallOut, I dont have to specify the exact instance of the item. So R u saying that I should pass the exact instance every time I Call a function on onCallOut?

Regards,
Mav

If you read the documentation and what ISCBorisB wrote - carefully - you'll see that FormAPI's event handlers automatically pass the specific item that triggered the event handler. From that item, if you need to, you can reference its name (xpath) and then use that to reference other fields within the same context - like:

var itemX = IWDatacapture.getItem(item.getName() + "../some_other_field");