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 am trying to generate a where statement a graph fex that will then be passed to the drilldown report as a parameter. I am doing fine with something like:
and then in the drilled report I replace the ~ with ' and have the WHERE statement just be WHERE &where_stm. My problem is that I have not been able to find a way to put values like N1 from the graph into the parameter phrase. If I add N1 to the SET statement it pushes over as N1 no matter what I've tried. I was hoping it would be as straightforward as putting the &CLAIM_STATUS_TYPE in the where statement was.
If anyone has any good tips on how to make things more generic when drilling down I'd be glad to hear them. I've searched these forums until I'm crosseyed, but nothing seems to be lining up for what I'm trying to accomplish. Basically I have multiple graphs that when drilled into will go to one centralized detail report, but each graph will have many different combinations of parameters.
Thanks for your time reading through this. I'm very new at this and probably over complicating matters.
Thanks!
rob
WebFOCUS 8.0.0.5 - SQL Server - Windows Server
Posts: 21 | Location: Fort Wayne, IN | Registered: June 29, 2007
Thanks for the reply Ginny. It doesn't quite address the complete issue I'm facing though, but I'm sure I'll be using this technique soon.
Where I'm having problems is getting the N1 value into the parameter. Right now for instance I am passing the claim status (new/pending/closed) that is a parameter from the HTML launch page. I then need to also pass the drilldown values such as Claim Type(property/casualty/etc) and Year/Month (2008_01) when a user click on the line graph to drill down into detailed data displaying Counts by Claim Type by Year/Month. If I put N1 into a SET or Define it is just displaying N1 as opposed to &vars which are parsed.
Is there a way to build a parameter string withing the drill FOCEXEC line? Once a space is encountered, it determines that a new parameter is being passed.
Thanks!
rob
WebFOCUS 8.0.0.5 - SQL Server - Windows Server
Posts: 21 | Location: Fort Wayne, IN | Registered: June 29, 2007
Just an idea. Why not add this N1 parameter (or even more params) as a separate parameter to your drill-down parameter list. Then in the target procedure you can do with it what you want. Point is, that this N1 parameter will only be resolved when the html-code for the report is being created, You can't do a thing with it in DM, because that is being eveluated before the request runs. And there is no real logic in building the focexec parameter line for drilldowns. As you noted, a space means "oh, good, I've got a new param", so why not use that to your advantage.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Thanks both for your comments. I feel like I am in a vortex right now and just needed something to grab onto regarding this drilldown issue. For the time being I will pass parameters to be joined together in the drill fex.
I'm sure there is a more elegant way to do this code, but I need to get the detail data to the users today or tomorrow on a bunch of graphs, so this will work the the time being... and later I can tweak the coding.
Thanks again!
rob
WebFOCUS 8.0.0.5 - SQL Server - Windows Server
Posts: 21 | Location: Fort Wayne, IN | Registered: June 29, 2007