Problem with multiple usages for shared dimensions

[Felipe Trevisan]

I´m getting an error (“XMLA Discover unparsed results error”) while trying to drill-down on a dimension created from a shared dimension. See attached picture.

One particular detail is that we´ve created two dimension usages based on same shared dimension (details on attached schema XML file):
- Shared Dimension: Area
- Dimension Usage: Emissor
- Dimension Usage: Executor

From “pentaho.log” file we can see:

2014-11-10 18:06:51,478 ERROR [mondrian.rolap.RolapCube] RolapCube.lookupChild: In cube "AT - Autorizacao de Trabalho" use of unaliased Dimension name "[Area]" rather than one of the alias names "Emissor" "Executor"
2014-11-10 18:06:51,478 ERROR [mondrian.xmla.XmlaServlet] Errors when handling XML/A message
mondrian.xmla.XmlaException: Mondrian Error:XMLA Discover unparse results error
at mondrian.xmla.XmlaHandler.discover(XmlaHandler.java:2873)
at mondrian.xmla.XmlaHandler.process(XmlaHandler.java:671)
at mondrian.xmla.impl.DefaultXmlaServlet.handleSoapBody(DefaultXmlaServlet.java:507)
at mondrian.xmla.XmlaServlet.doPost(XmlaServlet.java:318)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:643)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)

Seems like XMLA Provider is not using the correct dimension label/name to build MDX query.

I’m using latest version of XMLA_Provider: 1.0.0.19.
This configuration works fine on Saiku or Pivot4J plugins.

Another information: XMLA Provider works fine with shared dimension referenced by only one dimension usage.

Thanks in advance,
Felipe Trevisan

[Felipe Trevisan]

Screenshot

[Felipe Trevisan]

Schema XML File:

[Alexandra Davidoiu (Iancu)]

Can you attach the pentaho.log file? We need to know in what particular query is this dimension involved.

[Felipe Trevisan]

Here is the log file.
Thanks in advance.

[Alexandra Davidoiu (Iancu)]

Hi. Sorry for the late reply. Can you use the support mail/skype from here: http://www.arquery.com/Contact

We need to do a telco to fix this problem. The log file attached here appear to be from a different session (no drill).

[hassoalbert]

When dealing with shared dimensions across multiple aspects of a project or system, challenges often arise in maintaining consistency and clarity. Whether it's a software development project with multiple teams, a complex organizational structure with overlapping responsibilities, or even a shared physical space utilized by different groups, ensuring that dimensions like time, space, resources, for ios 18 update or objectives are consistently interpreted and applied can be a significant hurdle.

[kathrynmorrison2k@gmail.com]

When tackling shared dimensions across multiple aspects of a project or system, challenges often arise in maintaining consistency and clarity. Whether it's a software development project with multiple teams, a complex organizational structure with overlapping responsibilities, or even a shared physical space utilized by different groups, ensuring that dimensions like time, space, resources, or objectives are consistently interpreted and applied can be a significant hurdle. This holds true even for more specialized projects such as Logo Design NJ, where the coordination of design elements and branding strategies must align seamlessly with broader project objectives.

[felixhar risondavid]

Managing shared dimensions in multiple usages can be challenging, especially in complex data environments. Shared dimensions are often utilized across various fact tables to ensure consistency and streamline data analysis. However, when these dimensions are not properly managed, it can lead to data integrity issues and analytical inconsistencies. To address this, it's crucial to implement a robust data governance framework for Custom Diamond Grillz that includes clear guidelines for dimension creation, maintenance, and usage.

[james fenton]

It appears that the issue you're encountering with the “XMLA Discover unparsed results error” is due to the XMLA Provider not correctly distinguishing between the aliased dimension names when constructing the MDX query. Specifically, the log indicates that the shared dimension "Area" should be referenced by its aliases "Emissor" or "Executor." This issue might arise because XMLA Provider version 1.0.0.19 isn't properly handling multiple usages of the same shared dimension.

Since this configuration works with Saiku or Pivot4J plugins, the problem seems specific to the XMLA Provider. You could try updating to a newer version of the XMLA Provider if available, or reach out to the provider’s support for assistance. Additionally, reviewing the schema XML file to ensure all aliases are correctly defined might help. For further details on troubleshooting, consider exploring resources on Fintechzoom, which offers insights into such technical configurations.

[james fenton]

[james fenton]

I understand that you’re facing an issue with the XMLA Provider, specifically the "XMLA Discover unparsed results error" when trying to drill down on your shared dimension "Area." This can be quite frustrating, but let’s see if we can find a resolution.

From your description, it seems that the problem arises due to the unaliased dimension name "[Area]" being referenced instead of the intended aliases "Emissor" or "Executor." Here are a few steps you can take to troubleshoot this issue:

Review Dimension Usages: Double-check the configuration of your dimension usages for "Emissor" and "Executor." Ensure that they are correctly set up to utilize the shared dimension "Area."

Inspect the MDX Query: You might want to use tools like "ATT My Results" to examine the generated MDX query closely. This could provide insights into why the correct dimension label is not being utilized in the query construction.

Upgrade XMLA Provider: Make sure you are using the latest stable version of the XMLA Provider. If updates are available beyond 1.0.0.19, consider applying them as they may contain fixes for known issues.

Check Compatibility: Since you mentioned that it works well with Saiku and Pivot4J, it’s worth confirming if there are any compatibility issues specifically with the XMLA Provider and your current setup.

Consult Documentation: Sometimes, reviewing the documentation for the XMLA Provider can shed light on configuration details or limitations that may be causing the error.

Reach Out for Support: If none of these steps help, consider reaching out to the support forums or customer service for your XMLA Provider. They may have encountered this issue before and could provide targeted assistance.