Forum Discussion
Adding measure while using SSAS tabular datasource corrupt the whole report
Hello,
We have Power BI Server installed locally. We are using Power BI for Desktop optimized for Power BI Server (June 2017 version). We ran into some issues while creating report using an SSAS Tabular datasource.
We have a cube with +- 30 measures. A colleague created a PowerBI report with many different visuals / filters and everything works fine. As soon as she adds a new measure within the report, everything starts messing up where various visuals displays an "(X) Can't display the visual. See details" but surely, there's never any details to see (unexpected exception occured).
My first thoughts was that there was something wrong with the mesure definition that was added to the report. So what I did is take an existing measure from the cube and I've added a new measure in the report with the exact same definition except the define a new measure name.
So now, I have two treemap displaying both measures. As soon as I change the year from a slicer, everything starts messing up while it was not the case at all before I add a measure locally to the report.
So my question, is there known issues about adding measures to a report that is based on an SSAS tabular?
Thank you for any help.
Best regards
19 Replies
Hi Dars,
We you able to solve this problem? I am currently experiencing a very similar problem.
Setup
SSAS Tabular cube on Analysis Services SQL 2016 standard edition (build 13.0.4206.0)
A live connection is created through Power BI Enterprise gateway (14.16.6697.1)
Building a Power BI report with Power BI Desktop (septempber 2018) using dataset from PBI workspace
Everything is working fine until I created a report calculated measure based on 2 of the measures in the tabular model.
The measure I create is very simple Unitprice = DIVIDE([Sales Amount]; [Sales Quantity])
But when I add this measure my original [Sales Amount] measure stops working (and all other measures that use this in it's calculation), but measures that doesn't use [Sales Amount] works fine, so it's a "Semi" crash of my cube. If I reprocess the cube everything works again until a query is send using the report calculated measure.
Unfortunately no. It's clearly a bug. You either have to build your model directly on tables or add the measures in your cube to avoid this problem. Funny that the same measure works in the cube but screw up the whole thing when you add it on top of your cube directly in the model :-(
I have updated to October version, still no luck. I have also tried using the Power BI Desktop regular version to see if the result was different, again no luck.
I really think that this is a serious bug. I have create a simple new tabular cube with only one measure
:
YTD Sales Amt:= CALCULATE( SUM(Sales[SalesAmount]), FILTER( ALL('Dates'), Dates[CalendarYear]=MAX('Dates'[CalendarYear]) && 'Dates'[FullDate] <= MAX('Dates'[FullDate]) ) )This measure works fine without any problem in Powerpivot and also Power BI. Then when I add a measure manually in Power BI while connected to my SSAS tabular cube :
Top 3 Category = IF ( ISBLANK ( VAR Top3 = RANKX ( ALL ( Products[Category] ), [YTD Sales Amt] ) RETURN IF ( Top3 <= 3, Top3, BLANK () ) ), BLANK (), [YTD Sales Amt] )Again, it works fine. But when I change my slicer value from 2017 to 2016, then one of the graph starts displaying (X) can't display the visual. If I remove the measure I manually added, I still see this (X) even on the graph (Card) where I only show the YTD amount. It simply doesn't make any sense :(
We had a similar issue with a SSAS MultiDimensional data source. Built to a set os visuals. then added a local measure. Local meausre wokred fine until you changed a slicer. Removing the local measure still left the visuals broken. Restarting PBI Desktop didn't seem to help. The original (un amended) PBIX still gave us an error.
We had to restart the SSAS MD service on the server to get the visuals to work again (it was all direct query node)
The best thing was we could open the same PBIX on two different machines, leave one unchanged, produce the crash on the second mahcine and the unchanged one would now give an error! That's how we figured out it was happening somewhere on the SSAS MD server.
We tried to work up a repro but got pushed onto other work before we could get something concrete submitted to MS.
I have a Dataset created in PowerBI Service that is based on an SSAS Tabular model. The Dataset was created with 'Connect live' option.
Then I open up PowerBI Desktop, connect successfully to the Dataset in PowerBI Service and begin to create a report. I Selected something from my Date dimension and several measures. This worked fine. But there's was one particular Measure that was causing the report to fail with the error message: 'Can't display visual'.
I asked one of my colleagues at work to try the same set of actions that I did and for her it worked without any issues even when adding the measure that made my report crash. Weird!
At first I thought it was some permission issue but then if that is the case then I shouldn't have been able to connect to the Dataset and create the report in the first place (at least with the measures that were working).
I really don't know what the cause this but there was one action I took that solved the issue. I simply went to my SSAS Tabular model and did a Full Process through SSMS. And that solved the problem. But I really don't have an explanation for why this worked because if it did work for my colleague then why not for me?
