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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
I'm creating a MAS file off a MSOLAP datasource with measures and dimensions to be used in an OLAP enabled report with drilldown on the dimensions. A OLAP report works alright coming off this MAS file until I try to use a DEFINE field in the MAS file. This DEFINE field is calculating a percentage. Once I drop that DEFINEd field into the report and run it I get back an error message saying: (FOC11207) ERROR IN THE QUERY: (FOC11265) A DEFINE OR WHERE TEST OSAT_PCT SHOULD NOT REFERENCE MEASURE Q Osat<br /> Total Part of MAS file:
TABLE FILE FACT_CUBE
SUM Q_OSAT_TOTAL<br />
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE SET ONLINE-FMT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET AUTODRILL ON<br />
ON TABLE SET OLAPPANE TOP
The whole point of this is that I'm trying to create a shared calculated field within the MAS file for other reports to use. This way DEFINEs of calculated fields won't have to be created or included into every report.This message has been edited. Last edited by: <Mabel>,
Having the COMPUTE in the report does work. I've already done that. It's trying to have the calc in the MAS file is what I'm after. This way multiple reports can reuse that calc without computing it each time.
Should I assume that a calc in a MAS file can not be done this way?
When working with a Cube we don't have the opportunity to perform a Define ourselves on each record. So, the Compute, which is done after retrieval is always the appropriate method. However, if the calculation is known to the cube then it would be in the MFD as .. FIELD=name, PROPERTY=calculated measure, REFERENCE=expression ; (at least in the 7.1.2 release, plus the new COMPUTE data type )