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.
We have a Reporting Object that includes DEFINEs. When issuing an additional DEFINE via InfoAssist, the Reporting Object DEFINEs are available via the field list, and can be selected as part of the calculation, yet when the OK button is clicked to complete the definition, the following error is displayed: (FOC258) Fieldname or computational element not recognized: "the reporting object DEFINE field which was selected"
I suspect that there needs to be an "ADD" parameter associated with the InfoAssist DEFINE FILE command, but can't find a way to select it. Any suggestions? Thank you.This message has been edited. Last edited by: Joni Campbell - Europa Sports,
8009 Windows, HTML, AHTML, Excel In FOCUS since 1983
Solution, via the help desk: "You may need to add the DEFINE in the master file itself, and not in the Reporting Object, then at the Master file level it is not considered as a "dynamic" DEFINE. There is already a project to have this option in IA, it is case 72862009."
8009 Windows, HTML, AHTML, Excel In FOCUS since 1983
I am currently experiencing this problem. Defining the field in the master file does tend to alleviate this issue but is an annoyance having to drag the field down through all the hold files. It is 2015 and this issue still occurs.
Maybe you could JOIN back to the table with the defined field at the point in your focexec where you need it rather than carry it all the way through your code.
WebFOCUS 8.2.03 - Production WebFOCUS 8.2.04 - Sand Box Windows 2012 R2 Server HTML, PDF, Excel In FOCUS since 1980
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015