<div dir="ltr"><div>I'm not sure that the solution is without consequences. According to the javadocs of the XmlaExtra interface:</div><div><br></div><div>
<p class=""><font face="monospace, monospace" size="1"> <span class="">/**</span></font></p>
<p class=""><font face="monospace, monospace" size="1"> * Returns the defined properties of a level. (Not including system</font></p>
<p class=""><font face="monospace, monospace" size="1"> * properties that every level has.)</font></p>
<p class=""><font face="monospace, monospace" size="1"> *</font></p>
<p class=""><font face="monospace, monospace" size="1"> * <span class="">@param</span> level Level</font></p>
<p class=""><font face="monospace, monospace" size="1"> * <span class="">@return</span> Defined properties</font></p>
<p class=""><font face="monospace, monospace" size="1"> */</font></p>
<p class=""><font face="monospace, monospace" size="1"> List<Property> getLevelProperties(Level <span class="">level</span>);</font></p><p class=""><br></p><p class="">Have you tried similar calls on Microsoft Sql Server Analysis Services? We shold compare their implementation with ours.</p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 26, 2015 at 9:18 AM, Ingo Klose <span dir="ltr"><<a href="mailto:Ingo.Klose@incuda.com" target="_blank">Ingo.Klose@incuda.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Could anybody please shed a light on this issue?<br>
<br>
We would like to understand the problem better in order to contribute or find a viable workaround.<br>
<br>
Many thanks and best regards,<br>
Ingo<br>
<br>
-----Ursprüngliche Nachricht-----<br>
Von: Ingo Klose<br>
Gesendet: Donnerstag, 21. Mai 2015 21:02<br>
An: '<a href="mailto:mondrian@pentaho.org">mondrian@pentaho.org</a>'<br>
Betreff: AW: Mondrian 4 - Unsupported properties?<br>
<div class="HOEnZb"><div class="h5"><br>
Hi guys,<br>
<br>
we found the line in the source code, that breaks the XMLA call.<br>
<br>
<a href="https://github.com/pentaho/mondrian/blob/4.2/src/main/java/mondrian/olap4j/MondrianOlap4jLevel.java#L98" target="_blank">https://github.com/pentaho/mondrian/blob/4.2/src/main/java/mondrian/olap4j/MondrianOlap4jLevel.java#L98</a><br>
<br>
public NamedList<Property> getProperties() {<br>
return getProperties(true);<br>
}<br>
<br>
Apparently in Mondrian 3.x This call was made in a different class and passed false instead of true as parameter.<br>
<br>
<a href="https://github.com/pentaho/mondrian/blob/4.3/src/main/java/mondrian/olap4j/MondrianOlap4jExtra.java#L322" target="_blank">https://github.com/pentaho/mondrian/blob/4.3/src/main/java/mondrian/olap4j/MondrianOlap4jExtra.java#L322</a><br>
<br>
public List<org.olap4j.metadata.Property> getLevelProperties(Level level) {<br>
MondrianOlap4jLevel olap4jLevel = (MondrianOlap4jLevel) level;<br>
return olap4jLevel.getProperties(false);<br>
}<br>
<br>
We tested changing the parameter to false and the XMLAConnector works like a charm.<br>
<br>
But now we are wondering, what could we have broken with this change and secondly can we either get this change back in the official code or what could be a different solution (Mondrian.properties?)<br>
<br>
Best regards,<br>
Ingo<br>
<br>
--------------------------------------<br>
Date: Tue, 12 May 2015 14:25:48 +0000<br>
From: Ingo Klose <<a href="mailto:Ingo.Klose@incuda.com">Ingo.Klose@incuda.com</a>><br>
Subject: [Mondrian] Mondrian 4 - Unsupported properties?<br>
To: "<a href="mailto:mondrian@pentaho.org">mondrian@pentaho.org</a>" <<a href="mailto:mondrian@pentaho.org">mondrian@pentaho.org</a>><br>
Message-ID:<br>
<<a href="mailto:VI1PR06MB10232785F57FD4B88C17B6C9FEDA0@VI1PR06MB1023.eurprd06.prod.outlook.com">VI1PR06MB10232785F57FD4B88C17B6C9FEDA0@VI1PR06MB1023.eurprd06.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello all,<br>
<br>
We are trying to get the XMLAconnect Excel plugin to work with Mondrian 4. Unfortunately the MDX-queries seem to be incompatible to Mondrian 4, due to the use of some Member attributes. For example in the foodmart sales cube, it creates an MDX like this:<br>
<br>
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<br>
<br>
These are the four properties that break the query:<br>
<br>
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].[$member_scope] [Store].[Store Size in SQFT].[Store Sqft].[$scenario]<br>
<br>
According to this commit on git (<a href="https://github.com/pentaho/mondrian/commit/a2e4d05cac249c397cc08770c2daf110cab4a117" target="_blank">https://github.com/pentaho/mondrian/commit/a2e4d05cac249c397cc08770c2daf110cab4a117</a>) at least the first two properties are mentioned in the source code, although they are in a "missing properties" list.<br>
<br>
Are those properties not supported in Mondrian 4 and is there a way to prevent the query from running into an error?<br>
<br>
Any hints and pointers would be welcome.<br>
<br>
Many thanks,<br>
Ingo<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.pentaho.org/pipermail/mondrian/attachments/20150512/61439213/attachment-0001.html" target="_blank">http://lists.pentaho.org/pipermail/mondrian/attachments/20150512/61439213/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Mondrian mailing list<br>
<a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br>
</div></div></blockquote></div><br></div>