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 have an FML report with "ON TABLE SET FORMULTIPLE ON". In building the report I've pulled a level 1 field from the hierarchy as Consolidated and the total is correct. If I try to use a level 2 field from the hierarchy the number for that tag line as well as the original are wrong.
Thoughts? I'm fairly new to this and I'm not sure I can recreate it using the car file.
WebFOCUS 7.6.2 DB2, V5R4 Output: PDF
Posts: 16 | Location: Des Moines, IA | Registered: December 04, 2007
Having little info to go on here, I will add this....using FML is not necessarily the most efficient way to get data out of a hierarchy. I've used different methods before to create hold files and then used FML to format the report. I had great success doing this.
Prod - WF 7.6.4 Unix/Solaris - Self-Service, BI Dashboard, MRE Dev - WF 7.6.4 Unix/Solaris - Self-Service, BI Dashboard, MRE Databases: Oracle 10g, SQL Server 2000, DB2.