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.
Sorry for the newb question, but i am new and need help. A developer is building a .NET form that will send a querystring to a webfocus report that we will build. Two questions:
1. Can you recommend what needs to be sent to in the querystring, other than the variables and their values?
2. Can you provide some code that shows how the FEX gets the querystring values and integrates them into the report?
Thanks very much for your replies.This message has been edited. Last edited by: Kerry,
Can you show mw how the FEX code gets this value? (44) I apologize for not catching on immediately. Documentation on WebFOCUS questions is hard to come by on the web.
Ordinarily our FEX files load, and wait for the user to physically add parameters and then click the submit button. In the situation where the parameters are in a querystring, how does the FEX use the variables and "auto-run?"
WebFOCUS Documentation is not difficult to find. Try here: Information Builders Technical Documentation Library. Click on the "Quick Link" appropriate for the version you work with and download all the PDF documentation files. The Help on Developer Studio is reasonably good as well.
I don't understand the fixation with how variables are passed to the WebFOCUS program and I don't understand what you mean by "user ... physically add parameters".
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
Query String variables do automatically become "amper variables", but they are not automatically passed to the Reporting Server.
To pass a Query String variable to the Reporting Server you must add the something like the following under: WF Admin Console -> Configuration -> Custom Settings
<SET> VARNAME (pass)
Where VARNAME is the name of the variable from the query string that you want to be passed to the Reporting Server.
If you want to pass a series of amper variables to a report without going through that, you can send the list within IBIF_params.
e.g. The following passing &COUNTRY=ENGLAND and &SEATS=2: &IBIF_parms=COUNTRY%3DENGLAND%2C+SEATS%3D2
Its also worth noting that the entire query string is an amper variable itself.
e.g.
<SET> QUERY_STRING (pass)
Will make the entire query string as a variable available to a FEX.
Depending on what you're trying to do there is also "Global Amper Variables". These are defined with a && within a FEX, and will be carried from one running of a procedure to the next.
OK, I figured it out. To make the FEX dynamically get the variable, I had to remove the reference to a dropdown select in the WHERE clause. It was there because originally the user had to input a parameter after the FEX loaded in their browser. Perhaps that is the Autoprompt that Waz mentioned.
Thanks for all of the replies, except for those that referenced a "fixation" on my part.