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.
Has anyone with 8.2 had issues with the filters not being applied when using InfoAssist+. I've been told by Tech support that this is a known issue that programming is working on but this is a significant issue for our users. Any workarounds that people are using or just rolled back to a previous version of the software?
Thanks!This message has been edited. Last edited by: FP Mod Chuck,
Filters not working in Reports, Charts, Documents or Visualization? I haven't noticed anything like that. Could you give us an example of what's not working?
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
Filters not working in reports created in our previous version (8.0.09) that have a global variable.
We get an error message: Unknown error occurred.
I have a ticket open with them and they are working on it but I'm just trying to see if others who have had this same issue are using some sort of workaround.