Forum Discussion
Adding measure while using SSAS tabular datasource corrupt the whole report
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 :-(
Dars,
Thank you for your reply - I guess I will have to investigate this further to see if I can find a way to reproduce it everything and then report it to Microsoft.
I have now created an issue with this bug, if you want to support it to give it some attention please give it a vote up:
