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.
Hi, I have a fact and number of dimension tables joined to it through Cluster Join concept. I want to hide the key fields but as soon as I comment the key field from the Fact the corresponding join in the dimension fails. Is there a alternative work around for it .
Regards, SAMM
WF 8.2.0.1, MRE, BI Dashboard, Self Service, Dev Studio, MS Windows XP SP1, Apache Tomcat/6.0.20, Oracle 11 g, I.E. 9 Output formats: HTML, Excel 2000 and PDF,Active Reports
Posts: 60 | Location: USA | Registered: April 07, 2011
SAMM - are you wanting to hide the key fields from the InfoAssist users? If so, why not try creating a Business View of the cluster join? That way you can hide whatever fields you need to as well and organize the remaining fields in whatever way makes the most sense to the users.
I would not use a Business View in WF8. Use a Dimension View. This will allow you to create dimensions with hierarchies and designate the other fields as either measures or attributes.
This is the recommended approach. However, in WF 77 the Business View is your only choice.