Good Day,
As per update of latest binaries in .com to fix the link lookup issue as raised by martin, i've tested it again and found out that there still some issues in firing the onchange event during onload event of the pages. I've attached some screen shots for reference.
Thanks,
Ruben Guico
Rollbase PH
I suggest you fix your JavaScript handler.
Hi,
I've reviewed the script but it seems the real cause of the error is because the scripts in the onchange event of link lookup were invoked during population of the records from the link lookup upon selection in the parent lookup, i've attached some reference screen shots, onchange is fired onload as per update but shouldn't fire when the link lookup is populated with dependent records, it should only fire when i've selected a record from the link lookup.
Regards,
Ruben Guico
Rollbase PH
Perhaps Martin can help you.
Hi Pavel,
Just for confirmation,
The new behavior of the component is that it calls the onchange of the link lookup even though it hasn't changed value yet?.
Thanks
Piscoso Martin
onchange() is called explicitly since set of choices has changed
Hi Pavel,
I've retested on .com, Thank you very much for adding the handler on the link lookup where if (newValue != oldValue) it's the only time the onchange will fire, this handles the explicit firing when the data is loaded and the selection is not changed ^_^
Piscoso Martin
Rollbase.ph