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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
From our technicals: It sounds like you may have gone into the HTML code and changed the property for “operation” and changed the value to BY and you need to change it back to “OR”. But the safest thing to do is to remove the control from the HTML page, refresh the Parameters so the HTM page will prompt you to add the control again. The system will add the control correctly. Please do not go into the HTML code it will cause you more aggravation. If that does not work for you, then please open a case with Customer Support Services for additional assistance. The phone number is 1-800-736-6130, or access online at InfoResponse.
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004
I've had this problem as well. I think it has something to do with changes made in the report that the HTML page points to, and not necessarily a change in the HTML page - the relation between the two is very bewildering.
I just don't know why this is a solution:
But the safest thing to do is to remove the control from the HTML page, refresh the Parameters so the HTM page will prompt you to add the control again. The system will add the control correctly.
I have refreshed the parameters, and suddenly, other controls than the one you're trying to fix get messed up. For instance, the option values in a listbox (all entered by the GUI HTML Composer) disappear - probably because of a -DEFAULT in the report fex. I think it is very dangerous to refresh the parameters.
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server