Forum Discussion
SSAS MD cube measures not displaying
- 7 years ago
I figured this out. The cube in question was using a feature called "personalization extensions" that makes enhancements to the available members of dimensions. (The "personalization" process will add stuff into the session on the fly).
The DAXMD is apparently not happy with the use of this type of feature.
I'm still not sure why it would cause a problem. Perhaps, while it can detect the session calcs, the DAXMD is not sophisticated enough to interact with them. It would be nice if it would just avoid them rather than throwing out an error. My query didn't actually rely on any new calculations which were being defined in the session.More info:
I tried updating my MSOLAP client driver to the latest and it doesn't help.
https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers
I also tested to see what happens when I run the same DAXMD from SSMS and it works fine in there!
So this appears to be a problem that is specific to the Power BI code itself?
I figured this out. The cube in question was using a feature called "personalization extensions" that makes enhancements to the available members of dimensions. (The "personalization" process will add stuff into the session on the fly).
The DAXMD is apparently not happy with the use of this type of feature.
I'm still not sure why it would cause a problem. Perhaps, while it can detect the session calcs, the DAXMD is not sophisticated enough to interact with them. It would be nice if it would just avoid them rather than throwing out an error. My query didn't actually rely on any new calculations which were being defined in the session.
More info: