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.
We have migrated reports and every so often this error comes up when trying to maintain them. Is there a specific trace or something that can be turned on so I can see what the actual issue is? I think sometimes it's due to authority, sometimes it's due to the path of the stylesheet, sometimes it's due to a -INCLUDE path.
When I am just making quick fixes to some reports it has been taking me too long to completely overhaul them. I'd like to find what's causing the issue and just correct that one issue.
ThanksThis message has been edited. Last edited by: <Emily McAllister>,
WebFOCUS 8202M Client: Windows Server 2012R2/Tomcat 8.0/IIS Server: IBM i v7r2m0 MS-SQL
I am following up with you regarding your question about tracing in a report.
You can add the following to the top of the code:
-SET &ECHO=ALL; -? &
Run the report ( or add in -EXIT at appropriate spots) on the report output - right mouse click and view source. Scroll to the bottom of the file to see the resulting code with &variables resolved.
If you are running reports against RDBMS tables then search the forum for SQL TRACE.
Thanks for your insight, Rifaz. The fex worked fine directly from Dev Studio, but failed from ReportCaster and I couldn't figure you why until I read your post questioning publication. After publishing the "included" fex it ran successfully.
8009 Windows, HTML, AHTML, Excel In FOCUS since 1983
Did you figure out what the issue is? We are having the same problem, with only a few of our users, which are admin. The other admins don't have that issue.
- FOCUS Man, just FOCUS! ----------------------------- Product: WebFOCUS Version: 8.1.04 Server: Windows 2008 Server