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...

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...