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
Anonymous's avatar
Anonymous
Not applicable
8 years ago

Dars,

 

Try updating your version to the October 2017 Release version and try again. Lots of updates were added since June 2017 in the October release

 

Best Regards

 

  • Dars's avatar
    Dars
    Frequent Visitor
    8 years ago

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

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      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.

       

      • Dars's avatar
        Dars
        Frequent Visitor
        8 years ago

        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