Measures that work in Desktop don't work in Power BI Service

[LaMatt]

Hi there,

We are expericing some odd behavior with our reports recently (past week or two..). Measures that used to work in Power BI Service, and still work in Power BI Desktop, no longer work in Power BI Service, they simply return blank. All of the reports are connected to the same semantic data model with imported data, the size of the model is currently around 25 GB, and we are using Premium Per User Licenses. In some cases slightly re-designing the measures has helped, but they were never very complex to begin with.

The latest example is a simple measure that uses a 'dummy' date filter table to only show data within a given date range, while ignoring the relation to the normal date slicer, but syncing the date selection . A solution not that uncommon and refernced on this forum quite a bit.

CALCULATE([Value],

     FILTER('Date Dimension',

          'Date Dimension'[Date] >= EDATE(MAX('Date Dimension Extra'[Date]), -12) &&

          'Date Dimension'[Date] <= MAX('Date Dimension Extra'[Date])))

The example is mainly to underline how simple some of these measures are that arent working in Power BI Service. The service isn't taking a long time to load when evaluating these measures, it's simply as if it thinks there's no data available. However, the underlying measure [Value] does return data. And again, keep in mind, that the exact same measure using the same semantic model works perfectly fine in Power BI Desktop.

So given that the measure works in Desktop, and has worked before in the Service, it makes us wonder if Power BI Service starts 'acting' up with large data models after they reach a certain size? 

Thank you,

[lbendlin]

a =
VAR md =
    MAX ( 'Date Dimension Extra'[Date] )
RETURN
    CALCULATE (
        [Value],
        DATESBETWEEN ( 'Date Dimension'[Date], EDATE ( md, -12 ), md )
    )

Depending on other filters you need to throw in a REMOVEFILTERS or ALLSELECTED etc.