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.
Does anyone have recommendations on the best way to handle Customer relationship hierarchies in WebFOCUS. Does it have any native support for Nested tables, or bridge tables?
One way I've handled customer hierarchies in other data warehouse implementations is to use the Ralph Kimball recommended "Bridge Table" methodology. This method makes ad-hoc searching very simple. Is there a more search time efficient way to do this in WebFOCUS?
We also need to the ability to support multiple independent hierarchy "overlays".
Thanks, MikeThis message has been edited. Last edited by: Kerry,
WebFOCUS 7.7 Linux - RedHat 5 all output (Excel, HTML, PDF)
We're still early in the project and the format of the source is not known at this point. I believe it's going to be a Parent/Child self referencing table. The source database will be Oracle.
WebFOCUS 7.7 Linux - RedHat 5 all output (Excel, HTML, PDF)