As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I have 2 fields, say f1 and f2 to be chained. Both fields are populated by a fex and have a onchangeevent to run something. I noticed that once I change a value in f1, which triggers its onchange event and calls the f2 to be updated, the f2's onchange event will not work. The f2's onchange event works fine if f1's value is never changed.
I am thinking probably the f2's onchange event is lost once the f2 is updated by a fex due to the chained f1's value change. Please note f1 works fine and f2 would work fine if f2 is not populated by a fex.
Thanks.This message has been edited. Last edited by: Kerry,
This indeed makes sense. Think on it. When you chain two fields, what happens when field1 changes value is that a fex is fired off which providesa new contents for the f2 drop down box. Hence, the dropdown box has received a new contents from the backend, not because of some event the user caused. The latter is what triggers the onchange events. Re-populating is not an event from the viewpoint of the browser.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007