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.
The tree is weird; it's a general IBI facility and not really under our direct control. We use a special flag in reports to be able to translate the weird flag we get from the tree to the actual parms the reports use.
All dimension parms are classically:
[dimension_name]_levelnn_value
where nn is the level number and dimension_name is the uppercased name of the dimension, with spaces turned to underscores.
And those values are truncated by the tracing facility in WebFOCUS Client.
so &D00_DIMENSIO>= T &D01_LEVEL01_>= 2009 &D02_LEVEL02_>= 3 &D03_LEVEL03_>= 07
translates to:
&D00_DIMENSION_NAME>= T (e.g. the first dimension name is: T) &D01_LEVEL01_>= 2009 (e.g., TIME_LEVEL01_VALUE is: 2009) &D02_LEVEL02_>= 3 (e.g., TIME_LEVEL02_VALUE is: 3 - third quarter) &D03_LEVEL03_>= 07 (e.g., TIME_LEVEL03_VALUE is: 07 - seventh month)
Hope this makes sense.
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!
Thanks for the quick reply. Your message does make sense, but I think I may have been looking in the wrong direction and need your advice.
I am trying to over-ride the current period values set on the Manage tab. I have a report where I want to give the user a control to set current period and have the report display based on that. There are many different time ranges in use, which is why I didn't build a gadget for this.
I though that setting some time variables would do that, but I'm not having any luck. I've tried sets on all these variables so far, but it keeps showing the current period that is set on the managed tab's custom fex (pmf_set_date.fex):
Just to re-state my question, how do I provide PMF with a time dimension value and have my date ranges work off of that value instead of the current period that is set on the Manage tab?
Cheers,
Joey
Posts: 318 | Location: Los Angeles, CA | Registered: November 15, 2005
The variables are &TLVLnn_CUR, so it's not clear to my why you previous example was not working. Here's what I tried against the sample pmf_manufacturing DB:
Yes, this worked well. I suspect the problem is that I didn't have TIME as my &SORTBY1 variable. I was actually trying to use it as an across. Easy to change. Thanks so much, you are an excellent help.
Cheers,
Joey
Posts: 318 | Location: Los Angeles, CA | Registered: November 15, 2005