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 created a compound report using Document Composer. It has about 4 pages that consists of graphs and reports. I created separate fexes for each component and inserted them one after another in document composer. The report ran successfully originally. I had to make changes to some of the fexes and change the graphs from 3-D bar to regular bar graphs. I reimported each component in the correct order. The data displayed in document composer after I reimported each report and graph. After I ran the report and it came up, only the first report displayed data. All other reports and graphs did not display the data. I do not get any errors. When I run each fex interactively, they run successfully.
Can anyone tell me why that happens and what to do. Pasted below is the document composer code. Thanks.
From my experience, its hard to nail down the issue and even replicating the same with GUI.
Remove the -INCLUDEs from each component and embed the code instead. First begin with few components you may get a clue. If this doesn't work then i would try recreating it from scratch rather the spending time to debug it.
Most of the times I've faced this issue is because: 1) the reports overlap each other causing one of them to overshadow others - In this case, adjust the position and dimension(relative or absolute) 2) the reports which are invisible are out of bounds for the paper size - In this case, adjust the format of the report.
Quickest way to debug was to comment out the includes and the corresponding component in the layout designer on the top. Uncomment them one at a time and see the output.
We get the same behavior when there is an error in the compound document. No error displays on the report but only the first section renders.
If you run the document from AppStudio, hit the little drop-down to the right of the "Run" button and click "Message Viewer ON" and then run the report. This should give you visibility to the error that is causing the other reports to not render.
Server: 8009; Client: 8009 Refresh; OS: Windows Server 2008 R2 64-bit; Web Server: Tomcat; Output Formats: All
Posts: 9 | Location: Oregon | Registered: June 12, 2012
Sorry for the delayed response, but I had to put out a few other fires and was finally able to get back to this one. Thank you so much for this suggestion because this is the one that worked. The includes had dialogue manager labels in it. This meant that each of the report components were using the same label names so I did not get any data for any of the other reports and graphs except the first report. I followed your suggestion by including in composer only the portion of the includes that I needed. I then gave each dialogue manager label a unique name. Everything ran smoothly. It would have helped if I had gotten a WF error indicating duplicate labels. Special thanks to you, and thanks to all who took the time to respond to this post.
quote:
Originally posted by atturhari: From my experience, its hard to nail down the issue and even replicating the same with GUI.
Remove the -INCLUDEs from each component and embed the code instead. First begin with few components you may get a clue. If this doesn't work then i would try recreating it from scratch rather the spending time to debug it.