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 a report, that returns a error message when the date range is > certain amount of days. Everythign works as intended until i add a where clause condition of:
All parameters are successfully passed but when i add this static condition, my retrun error message (that is being passed from a sql stored proc successfully) is not visible, just a empty report
Why would my header keep dissappearing when the static condition is added?This message has been edited. Last edited by: Tamra,
SQL SQLORA
EX <stored proc>;
TABLE FILE SQLOUT
PRINT *
WHERE <type fieldname here> EQ <type condition here>;
END
The stored procedure returns stuff then webfocus filters it out.
Or, you can add the filter to the stored proc like you said.
Or, you can put whatever native sql code that your database will process between the SQL and ; and it will get sent to the db and let the db run it. Basically, if the sql code will run in your db, you can put it between SQL and the ; and it will run.