XMLA driver should encode colons in property names.
See https://sourceforge.net/p/olap4j/discussion/577988/thread/6a690a3c/ and http://jira.pentaho.com/browse/PRD-3825
"::PENTAHO-REPORTING::PORT" is actually a valid XML element name, but SSAS doesn't think so, and they write the SSAS standard. So the olap4j XMLA driver should convert each colon to 'x003a'.
I meant 'underscore x003a underscore' above. Markdown screwed up my comment.
We should encode non-alphanumeric characters in properties.
Microsoft does not specify that is a valid property name, but their built-in properties are all UpperCamelCase; see http://msdn.microsoft.com/en-us/library/ms186627.aspx.
I STRONGLY recommend that people adhere to that standard for property names. (Start with alpha, subsequent characters alphanumeric.) Even underscores will cause problems, because we will encode _ to 0x005f and that may confuse the server receiving the request.
This is probably not a problem anymore. We filter out the unknown properties.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.