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 wonder if anyone knows if this is a known issue in wfc OLAP. When I coded a table file command with a where clause with OLAP on, the first execution returns immediately. But, after removing some dimension selection on the control panel and executing a re-run, it churned and churned and nothing returned and the browser timeed out. Now, if there is no where clause, first run and subsequent runs all returned immediately.
Is it because WFC can't deal with where clause with OLAP on?This message has been edited. Last edited by: Kerry,
wf 7.6.11 unix aix active reports, HTML, Excel, Text and PDF formats
It may have something to do with the names of the dimensions. Something like that happend to me, and it ended up being something silly like the OLAP dimension was named DIVISION and the where statement had DIVISIONS (with an S).
Erfan WF 7.6.9. Dev Studio/BID/Info Assist/Report Caster/MRE
well, sadly no. I can't reproduce on the car file. Maybe it is too small for the issue to manifest? When I ran mine, I heard the pc grinding away. It was as if wfc studio was doing all the data filtering on the pc itself and the file was too big for it to process before the browser expired.
wf 7.6.11 unix aix active reports, HTML, Excel, Text and PDF formats