Problems with Mondrian 4

[Ingo Klose]

Hi,

we are evaluating XMLAConnect with Mondrian4 and are running into a strange problem. We can conncect to the OLAP Server and select a cube and all.

If you pull a measure into the pivot table all is well, but as soon as we pull a dimension into the columns or rows we get an error like this:

Mondrian Error:MDX object '[Product].[Products].[Product Family].[IS_PLACEHOLDERMEMBER]' not found in cube 'Sales'

Do you guys have any idea what the problem could be?

Best regards,
Ingo

[Ingo Klose]

By the way...this is the MDX that is created when you drag an attribute to the columns:

SELECT NON EMPTY Hierarchize(AddCalculatedMembers({DrilldownLevel({[Store].[Store Size in SQFT].[All Store Size in SQFTs]})})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME,[Store].[Store Size in SQFT].[Store Sqft].[CATALOG_NAME],[Store].[Store Size in SQFT].[Store Sqft].[SCHEMA_NAME],[Store].[Store Size in SQFT].[Store Sqft].[CUBE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[DIMENSION_UNIQUE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[HIERARCHY_UNIQUE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[LEVEL_UNIQUE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[LEVEL_NUMBER],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_ORDINAL],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_NAME],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_UNIQUE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_TYPE],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_GUID],[Store].[Store Size in SQFT].[Store Sqft].[MEMBER_CAPTION],[Store].[Store Size in SQFT].[Store Sqft].[CHILDREN_CARDINALITY],[Store].[Store Size in SQFT].[Store Sqft].[PARENT_LEVEL],[Store].[Store Size in SQFT].[Store Sqft].[PARENT_UNIQUE_NAME],[Store].[Store Size in SQFT].[Store Sqft].[PARENT_COUNT],[Store].[Store Size in SQFT].[Store Sqft].[DESCRIPTION],[Store].[Store Size in SQFT].[Store Sqft].[IS_PLACEHOLDERMEMBER],[Store].[Store Size in SQFT].[Store Sqft].[IS_DATAMEMBER],[Store].[Store Size in SQFT].[Store Sqft].[DISPLAY_INFO],[Store].[Store Size in SQFT].[Store Sqft].[VALUE],[Store].[Store Size in SQFT].[Store Sqft].[$member_scope],[Store].[Store Size in SQFT].[Store Sqft].[$scenario],[Store].[Store Size in SQFT].[Store Sqft].[CELL_FORMATTER],[Store].[Store Size in SQFT].[Store Sqft].[CELL_FORMATTER_SCRIPT],[Store].[Store Size in SQFT].[Store Sqft].[CELL_FORMATTER_SCRIPT_LANGUAGE],[Store].[Store Size in SQFT].[Store Sqft].[DISPLAY_FOLDER],[Store].[Store Size in SQFT].[Store Sqft].[FORMAT_EXP],[Store].[Store Size in SQFT].[Store Sqft].[KEY] ON COLUMNS FROM [HR] CELL PROPERTIES VALUE, FORMAT_STRING, LANGUAGE, BACK_COLOR, FORE_COLOR, FONT_FLAGS

Is there a way to slimm this down or control which attributes are used?

[Ingo Klose]

Those 4 items break the query [Store].[Store Size in SQFT].[Store Sqft].[IS_PLACEHOLDERMEMBER],[Store].[Store Size in SQFT].[Store Sqft].[IS_DATAMEMBER] and [Store].[Store Size in SQFT].[Store Sqft].[$member_scope],[Store].[Store Size in SQFT].[Store Sqft].[$scenario]

Is there a way to surpress those? Are the really needed?

[Alexandra Davidoiu (Iancu)]

Can you send the schema you are using to the support address listed here: http://www.arquery.com/Contact ?

We might also need to look on your particular setup for Mondrian but this is definitively doable.

[metholdakaarison]

Mondrian 4, despite being a powerful tool for data visualization and OLAP (Online Analytical Processing), has faced several notable problems that limit its usability and adoption. One major issue is its steep learning curve and lack of comprehensive documentation of ts game, which can be frustrating for new users trying to configure and deploy the system.