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.
It's happening because PMF has three fields for FORECAST: FORECAST, FORECAST_NUMERATOR and FORECAST_DENOMINATOR and in the FOCEXEC you're running the server is configured to allow partial field names (it's the default).
You can set this to strict, by setting SET FIELDNAME=NOTRUNC in your FOCEXEC.
It doesn't happen in PMF FOCEXECs because we do it automatically in FILTERS.FEX, which is run whenever any content is called through the PMF MRE domain. You can embed SET FIELDNAME=NOTRUNC in your custom FOCEXEC. I don't recommend put it in EDASPROF.PRF (that's a hack and could affect other developers who assume it's on).
thanks
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!
At this point, this PMF is pretty much out of box, no customization of any kind. A few dimensions and one measure is loaded. It is true that there is a WebFOCUS environment at this location and this WebFOCUS environment has been around for a long time. This WebFOCUS app server environment is reporting from Banner ERP.
So somehow, in PMF, that was freshly installed a few weeks back, missing FIELDNAME=NOTRUNC?
In 5.1.2 you can either put it into FILTERS.FEX which should be getting called in site.wfs for the PMF Domain; or you could, if you choose, put it in EDASPROF, which would make it global everywhere.
thanks
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!
I'll be even more precise because I've been way too imprecise!
For 5.1.2, we're recommending that if you get this error, to SET FIELDNAME=NOTRUNC either in FILTERS.FEX (very recommended) or in EDASPROF.PRF. This is so that WebFOCUS doesn't get confused when a HOLD file contains FORECAST and FORECAST_NUMERATOR and FORECAST_DENOMINATOR, and the request asks for FORECAST, etc.
Post 5.1.2, we've made sure the couple places in PMF code where this was not absolutely explicit about what fields are needed so there can be no shorthand field issues, got made perfectly explicit. So you won't need this setting any more after 5.1.2.
thanks
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!