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.
Hi All, I'm wondering if anyone knows a way to have InfoAssist accept changes made in the code (Edit Source). I'm finding that when I edit the source for anything InfoAssist won't do (ie subtotal for selected columns only) I cannot open the report in InfoAssist ever again, without having it overwrite my changes and essentially revert the report back to before my coding changes. This means, once you change any code you cannot edit that report using InfoAssist again. Thanks in advance.This message has been edited. Last edited by: TRue,
InfoAssist only - Version: 7703 Windows 7 Excel and PDF outputs
I believe I specifically posted this question in the InfoAssist Forum... a GUI, yes... and maybe you have the convenience of other tools, but I don't right now, so I'm looking for a solution within the parameters I've been given.
InfoAssist only - Version: 7703 Windows 7 Excel and PDF outputs
TRue funnily I have had the same problem and have given up trying to get an answer, so like jgelona, I'm only using the InfoAssist to generate code so that I can then input it into the editor... it seems a bit stupid to allow you to edit the code then not let you see how it works without running the whole report each time..
It is not just InfoAssist, it is all the GUI tools. If you need to do something the GUI can't handle but you can manually add it to the code, forget about ever using the GUI with that fex again.
Even something as simple as adding comments to the code. Open the program in the GUI and save it and all the comments are moved to the top of the program (which is the 3rd reason I never use the GUI tools).
If you are stuck using the GUI, then I suggest you open a case with IBI and have them show how to do what you want to do in the GUI or put in a NFR if it can't be done in the GUI.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
I'm sorry in advance to comment on a thread this old.
I do exactly this without issue in WF7703, but on our upgrade to 8105 I now cannot even open it in 'text editor' then press save (no changes) without losing the ability to use InfoAssist. Surely this is not by design.
Has anyone had any updates or other experiences with this?
PROD: WebFOCUS 7.7.0.3 IBM i series and DB2 for i DEV: WebFOCUS 8.1.0.5 IBM i series and DB2 for i
I just created a report in IA and saved it. Then edited this report with Text Editor. My SAVE button is grayed out. If I SAVE AS and click the same report name and say YES to replace, then the report will no longer open in IA. However, just opening the report with Text Editor didn't take away IA availability. I'm running 8105.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
I have encountered this issue as well. One thing I noticed is that if I ran my report after making text edits, then saved it, that is when I experienced the issue.
If I recall, making the edits then saving the report without running it made the GUI editor available still.