Forum Discussion
Date import SSAS Cube live connection
Helper IAny known plan to change this behaviour?
Using dates for any serious business PowerBI report is critical. Not being able to use dates as dates :smileysad: makes selecting the data you want to analyze extremely hard.
We have an SSAS with dozens of nice calculated measures for previous periods and the like, our PowerBI users love PowerBI ... but working with date periods is simply painfull!
Helper ILife is curious. After some weeks dealing with this problem I found last friday the authorized answer of Microsoft on this post: no way to have dates as dates on PowerBI coming from SSAS live.
Five minutes later (literally, five) I saw one of my colleagues using an SSAS live date field as date on PowerBI. I was astonished ...
-How did you do that?
- I did nothing. I took one of your test databases, tried it, and it works. Good job! When will we upload it to our production systems?
I run to my desk and have been trying for hours. Same field, defined exactly the same way; same dimension defined exactly the same; everything seems identical, but it works on one OLAP SSAS cube (test) and it doesn't on another (the full company SSAS). No way to make it fail on the test olap; no way to make it work on the production olap.
Checked everything I could imagine, added hierarchy, dropped it. Defined flexible/rigid relationships. I cannot see the slightest difference. Tested and tested and tested again. Nothing.
So now I face the fact that it can be done ... but I don't know how neither why!!
Any idea :smileywink:
- vrocca
Advocate IV
Sounds like your issues was with a Multidimensional SSAS cube? Any idea if/how to get it to work on a Tabular cube?
It appears its not that straight forward. My dimension already is defined with order by key and yet the same behaviour.
Date.Value also will not show if its part of a hierarchy or if its attributehierarchyenabled is false.
