Forum Discussion
Adding measure while using SSAS tabular datasource corrupt the whole report
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.
Thanks for your reply. It doesn't really fix my problem but at least I know that I'm not crazy :-)
Therefore, we will avoid adding manual measures in Power BI report on top of a cube for now :(
Cheers
HI Dars,
I might be misunderstanding but I think the problem is because you are using a SSAS Tabular datamodel, not a local PBI datamodel. Thus you need to add the measures to the remote SSAS data model. Same for SSAS MD I would have thought?
If you have chosen the SSAS Tabular data connection my understanding is that the data is coming direct from SSAS, not being stored in the local PBIX, so not able to add measures or calculated columns in the local data model.
Anybody else agree / disagree?
Rob
The following article suggests that you can't add measures when using a Live connection.
However the following article says you can (section pulled out)
https://docs.microsoft.com/en-us/power-bi/desktop-analysis-services-tabular-data
Question: If I created a live connection, can I edit the model or query in Power BI Desktop?+
Answer: You can create report level measures in the Power BI Desktop, but all other query and modeling features are disabled when exploring live data.
This second version is why PBI Desktop allows you to add measures in a Live connected report, though the table page and data model are hidden. Shoing the Data model would be crazy useful, as would sample data. Why these aren't shown in a READ ONLY mode I'm not sure, they are inherently there in the backend, they're just obviosuly not being passed to what is now a dumb client app! It's just that as these measures get more complex (changing the context for example) they seem to cause issues on the SSAS backend. Like behaving badly as described above.
Like many early versions of MS software its a bit rough around the edges...
Hi Anonymous,
I think the question / Answer you highlight only applies if you have IMPORTED the data into a local PBI data model, and are then effectively working off-line to the SSAS Tab data. And Not if you are using a Live SSAS Tabular connection. Reading the introduction to the link you provide seems to confirm this, but the answer to the question you highlight is not very well phrased.
My opinion remains that if you use the Live connection, and thus get updated SSAS Tabular data everytime you load the PBI report you cannot create local measures and calc columns.
Rob
Hello Rob,
I understand but I would not allow to add local measure if the source doesn't permit it. Whenever a user have a specific need for a report, I don't want to add tons of measures covering all theses particular needs in the cube for a single report. We already have a lot of measures and I like having the flexibility defining ad-hoc measures in the PBI model.
The funny thing is that when add a local measure and it works, so the mechanic is there. But everything gets messed up whenever a slicer selection is changed.