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 SQL-passthrough in my fex and then I want to create a drop-down list in Resource Layout Painter to be able to pick 'list-of-values' from a table.
However, when I click the tick-box 'Dynamic' for the control of the parameter Developer Studio kicks out without error messages....just ends my session....very frustrating!
I've tried to add 'TABLE FILE <existing table> END' to have a reference to the WebFOCUS server since I'm using SQL-passthrough.
It's imperative for me to be able to use dynamic parameters together with SQL-passthrough...user friendliness is of high importance.
What release are you using? What steps are you going through to create the procedure with the resource layout tool? Any reason, in particular, for using passthrough? Can you give us an idea of your prcoedure?
Posts: 346 | Location: Melbourne Australia | Registered: April 15, 2003
Ohh...missed the procedure. 1. Create the report separately. 2. Create new report with RLP. 3. Insert current report. 4. Change parameter field to drop-down list. 5. Tick 'Dynamic'.
When I do that WebFOCUS crashes completely...and disappears.
I got the same behaviour on 526. However, I didn't find it coupled with pass-thru syntax. I got it as soon as I picked Dynamic. In 532 it works fine for me.
When filling a list box with values using pass-thru SQL in the dynamic procedure I need to run the data through a HOLD file before going for XML to get it to show. But, you probably already knew that.
Exampel:
SQL SQLMSS select account as ACCOUNT, account as ACCOUNT from RESULT group by account order by account; TABLE FILE SQLOUT SUM ACCOUNT BY ACCOUNT ON TABLE HOLD END TABLE FILE HOLD SUM ACCOUNT BY ACCOUNT ON TABLE NOTOTAL ON TABLE PCHOLD FORMAT XML END
well...the problem actually seems to be related to pass-through after all...
When using pass-through and specifying instance the RLP apparently doesn't know where to search for master-files since no connection is opened.
What I did was simply to add two reports in RLP. Both reports has to use the same parameter names for this work-around to function properly...and it's important that you do it in correct order...I've tested various ways and this seems to work:
1. Prepare a report using any master-file...include the parameter-name you want to use in your final report. 2. Open RLP and add the 'fake'-report you've created in #1, your parameter(s) will show up. 3. Alter your parameters as you wish them to appear, select dynamic and assign master-file to pick your 'list-of-values' from. 4. Add the report you want to show in RLP. 5. If you want to you can delete the 'fake'-report now, I would suggest that you test-run your report to see the parameter work first. 6. Save.
It's very important that you add the 'fake'-report first and that the parameter names used in both reports are identical.
Good Luck.
Ted
PS! The issue has been filed with IBI and hopefully there will be a correction made so that RLP/Developer Studio doesn't shut-down when this situation turns up.