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.
There are a ton of reports for one of our departments that ask the same 2 params every time you run them.
Term_Code Aid_Year
Here is the issue. All of the term_codes can only belong to one aid_year.
Ex: term_code 201380 (aug 2013) will always be in aid year 1314. 201410 (jan 2014) will always be in 1314 also.
Can I make some type of include file that figures out the aid_year param for you?
Because of the joins and how the data is, aid_year has to be passed or you do not get the expected results. Mainly 40 years worth of people fat fingering data entry is my guess.
So we need to pass both params, but it seems redundant to have to enter them both.
I could do a chained dynamic pull down for term_code, but I not a big fan of pull downs that have 40 values in them. Like the ones for birth year that take you off the browser sometimes.
I am thinking like a file that has 40 where/then clauses.
WHERE &termcode = '201360' OR '201370' OR '201380' OR '201410' THEN &Aid_year = '1314';
WHERE &termcode = '201260' OR '201270' OR '201280' OR '201310' THEN &Aid_year = '1213';
etc.
Has anyone done anything like this?This message has been edited. Last edited by: Greg,
prod: WF 7.7.03 platform IIS on Windows 2007, databases: Oracle, , MSSQL
Yes doing an include fex that will assign the &AID_YEAR parameter for you is a solution
-* aid_year_assign.fex
-* Assign aid_year based on &Term_Code
-SET &AID_YEAR = IF &TERM_CODE '201360' OR '201370' OR '201380' OR '201410' THEN '1314'
- ELSE IF &TERM_CODE '201260' OR '201270' OR '201280' OR '201310' THEN '1213'
- ELSE '1112';
-* END of aid_year_assign.fex
But it become a static solution.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
As far as I understand, the code that I gave you must be used as an -INCLUDE in the fex that produce the report. There is no need to be chained for a drop list. The user just have to select the Term_Code then the Aid_Year will automatically be assigned for the report data extraction.
Am I right when I assume that the user don't need to select the Aid_Year ?
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013