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 need help editing a fex file based on a SQL stored procedure created through the SQL Wizard in 7.1 The report runs fine, but a user has requested we run the report output as an excel file. When I attempt to enter the report painter to make the change, I am prompted for my SQL Stored procedure variables. Even though I am entering the proper variables, it always returns "error parsing master file SQLOUT' follwed by "the description cannot be found for file named: SQLOUT".
So it works from dev studio and the MR dashboard, but I can no longer open it in 'painter' to change a simple setting. (additionally I have this file in managed reporting (using the -mrnoedit funtion) and locally as a project, and get the same error in both).
Well not having 7.1 yet and this new Wizard, I can say this does not surprise me. The same thing happens trying to change a Fex in Report Painter, sometimes. Sounds like you are just going to have open it and edit the code, change whatever the output now is to EXL2K. I would open up a case with IBI and get an "official" reason for this phenomenon
Posts: 1903 | Location: San Antonio | Registered: February 28, 2005