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’m using a FEX to populate a drop down list in HTML Composer. This drop down list is chained to a radio button control that filters what the drop down list is filled with depending on what is selected in the radio control. In one radio button selection, I may need to add an ‘All’ option to the results that populate the drop down list. If the other two options on the radio button are selected, I will not need the all option. I don’t believe I’ll be able to use the ‘Add ALL option’ on the properties of the drop down list since I don’t always want the ALL option. This leaves me with adding a record to the report results from the FEX that populates the drop down list based on what criteria is passed to it from the chained radio control.
How do you programmatically add a record to a report? The report is currently being populated directly from joined tables.
Thanks, shelz.This message has been edited. Last edited by: Kerry,
"I'm new to focus" - "branching to a conditional modify" - These are mutually exclusive.
Look into the MORE command with which you can concatenate more than one file. You can bypass the second file depending on a condition. Here's an example:
-SET &COND_VAL = EDIT(&YYMD,'$$$$99$$');
TABLE FILE CAR
SUM
COUNTRY
BY COUNTRY
WHERE NOT COUNTRY CONTAINS 'I'
ON TABLE HOLD AS H001
END
TABLE FILE CAR
SUM
COUNTRY
BY COUNTRY
WHERE COUNTRY CONTAINS 'I'
ON TABLE HOLD AS H002
END
TABLE FILE H001
SUM
COUNTRY
BY COUNTRY
ON TABLE PCHOLD FORMAT XML
-IF &COND_VAL EQ '01' GOTO BYPASS1;
MORE
FILE H002
-BYPASS1
END
Francis
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
When you check the "Add ALL Option" properties box, HTML Composter adds a parameter named dynalldisplayvalue to the HTML statement for the object and sets its value to "ALL" (dynalldisplayvalue="ALL"). So I would imagine that one could use JavaScript to dynamically change the value of this parameter.
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
Well, I've tried a couple of things and not found a solution for only including ALL when needed.
I was able to add the all option to the FEX that populates the drop down list based on criteria passed to it. When I run the FEX stand alone, the all option displays as expected depending on the criteria passed. However, for some reason, when it is used to populate the drop down list, the all option never displays.
So I pursued only adding the all option in JavaScript when needed. For some reason, the event which is on the onlick of a radio button span always fires twice, adding all twice.
I give up going this route. I'll just change the report to accept the radio button parameter, leave the all on for all options and filter the report on the radio type selected. This involves more changes than I wanted to make, but I don't want to open an issue with IBI, and this may make the report function better any way.