Forum Discussion

AKirk's avatar
AKirk
Regular Visitor
2 years ago
Solved

Measure in graph returns inconsistent results when published to Service

I have an issue where a graph that works fine in Desktop breaks when published to the service. Here is what it looks like in the desktop app: And here is what the same graph looks like when...
Need Help
  • AKirk's avatar
    AKirk
    2 years ago

    I believe I have found the issue. It appears to be a case of auto-exist making assumptions, as detailed here:

     

    https://www.sqlbi.com/articles/understanding-dax-auto-exist/

     

    Setting filters on fields outside the summary table makes the results consistent between the desktop app and the service. The original data set uses references to other tables in a couple areas, which happen to be the areas I need to filter by.

lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
2 years ago

Use a Quick Measure for a more robust computation of your pareto.

AKirk's avatar
AKirk
Regular Visitor
2 years ago

Using a quick measure to get a running total of the number in question, totaled when the Cause changes, also produces inconsistent results. It gives the correct total in the desktop app (treating the causes in alphabetical order, instead of numerical order, but that is fixable), but it gives the wrong total when published to the service.

 

This is the auto-generated quick measure:

 

intercause running total in Cause = CALCULATE( SUM('SampleSum'[intercause]), FILTER( ALLSELECTED('SampleSum'[Cause]), ISONORAFTER('SampleSum'[Cause], MIN('SampleSum'[Cause]), DESC) ) )

 

In the desktop app:

 

In the service: