SSAS 2012 MD Calculations are not working

[parry2k]

Hello,

I'm using SSAS 2012 MD connector with PowerBI and we created few calculation on our cube, like YoY Growth, YoY Growth %, MoM Growth, MoM Growth %, in BI Desktop I only get value for "current dates"  when I use date calculations from SSAS and if I choose any other calculation, I get NA. I'm wondering if this feature is still not available in current SSAS connector.

Thanks in advance,

P

[HarrisMalik]

@parry2k you can use the time calculations created in OLAP cube. They are shown as seperate dimension under the original dimension. Can you please share your screen shot so I can better understand the scenario?

[parry2k]

Hey Harris,

Here are the screen shots, one shows dimensions added to the data model and other shows what that dimension contains:

Dimension ValuesCalculated Dimension in Model

Hope this is helpful. When I filter data on "current dates", i get the value but if I filter data on any other field, I get NA. At the same time I wrote MDX query and tested the result, it works fine.

Thanks,

P

[parry2k]

Does anyone has input on this or tried using the calculated fields from SSAS MD ? Would like to hear if it is a known issue with SSAS live connector or something I'm not doing right.

Thanks in advance,

P

[greggyb · Accepted solution]

This sort of date calculation is typically implemented with Named Sets in MD, which are not supported yet in the Gateway.

[parry2k]

Thanks a lot. At least it will give me closure that I am not doing something wrong.

[meysun]

SSAS MD support in Power BI is the closer to what is supported in Power View. Even in Power view Chris called out the below

http://blog.crossjoin.co.uk/2012/11/09/power-view-on-ssas-multidimensional/

'The consensus in the session room was that the SSAS team had done a really good job thinking through all the details of how this will work. In general your existing cube will not need to be redesigned, it will just work and all your queries and calculations will return the results you expect

But some things are not supported: if you have named sets or actions they will not be exposed; in some scenarios calculated members on non-measures dimensions will not be exposed either, but time utility dimensions should work; and cell security is not supported either – if a user is a member of a role that has cell security applied, they will not be able to run DAX queries.'