Forum Discussion

Dars's avatar
Dars
Frequent Visitor
8 years ago

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 SSA...
Power BI Report Server
SSAS
sdjensen's avatar
sdjensen
Solution Sage
7 years ago

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.

Dars's avatar
Dars
Frequent Visitor
7 years ago

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 :-(

  • sdjensen's avatar
    sdjensen
    Solution Sage
    7 years ago

    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.

      • muchinski's avatar
        muchinski
        Resolver II
        7 years ago

        Hello Dars and sdjensen,

         

        Just for a quick checkpoint: I've downloaded the files on the bug report, restored the database and used the Power BI file 20181004_ReportMeasures_4_TestReportWithReportMeasureDirectSSAS.pbix on the latest version of Power BI optimized for Report Server, as well as the latest cloud version. Everything ran fine here.

         

        The difference is that my environment is running with the latest PBIRS version ( 2.61.5192.641 64-bit (August 2018)) and also my SSAS is 14.0.204.1 (SQL 2017 CU5) - It is not the last CU because of a bug on SSAS from CU6 that closes a connection when updating the model...lol...

         

        Nevertheless, version June 2017 is not supported anymore.

        My thoughts here after reading sdjensen post: It should be an SSAS problem. Did you try to use SQL Server Profiler to trace your queries on the SSAS side and check if it gives you some error message?