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.
Did you make any edits via the source? I've found that after any text edits I would need to immediately open the report in the GUI and save it. Otherwise, I'd find that the option to edit would no longer be available.
There's an issue/bug with the role privilege for allowing others to edit via Reporting Objects in IA+ in 8202M that has been present for I'm not sure how many releases. If you no longer see the option to edit in the new WF Home UI, try editing from the Legacy Home page instead. It should be present there at least if your issue is this issue. That's the workaround we've been utilizing.
Another issue with IA+ is that if your using a filter clause created with the Expression Builder feature, depending on what you put in there, it can bork your ability to edit/open the report/chart/etc. Also, creating DEFINE/COMPUTE fields sometimes kill it as well.
Mike mentioned the editing the source manually bug already.
I could go on, but most likely you'll need to determine whether it's viable and desirable to upgrade out of the issue. Case workers love to ask if we have upgraded after the 1-4 months of not responding back to us happens, finally chiming back in asking such after the 1 initial attempt of resolving the issue ends up at the "Please give us all your log files and stack traces and we'll get back to you..." response. Then, if you do upgrade, you welcome 12 new bugs even though the one is fixed, if you're lucky.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015