Forum Discussion

thgrogan's avatar
thgrogan
New Member
2 years ago

Cards With Values Controlled by Slicer Stopped Working Last Week

We have a tabular model deployed to Power BI. Within this model we have a number of metrics as well as a Calculation Group for Time Intelligence Metrics. Within this calculation group we have an additional calculated column that groups the different calculation items. For instance, Current Month, Previous Month, and Change From Previous Month are all tagged as “Month”, while Current Quarter, Previous Quarter, and Change From Previous Quarter are all tagged as “Quarter”. 

Then we have separate dashboards that are connected to this model that are deployed to the environment as well. Some of these dashboards have a feature where a metric is displayed as a card. This card will have the Time Calculation Items as a visualization feature. For instance, we would apply a basic filter where only Current Month and Current Quarter are selected. We then have a single slicer filter on the dashboard for the Calculation Group options (Month and Quarter). This way, when a user selects “Month” the value of the metric for “Current Month” is shown and if they change it to “Quarter”, the value for “Current Quarter” is displayed instead.


This was working without errors up until last Tuesday (11/21). Now, no matter what is selected in the Calculation Group slicer, the cards just display as Blank. What is interesting is if we copy/paste the visualizations into the model file, it works as expected. They just don’t work when the dashboard is connected to the deployed model. 

 

Any help here is greatly appreciated!

Need Help

1 Reply

  • freginier's avatar
    freginier
    Icon for Solution Sage rankSolution Sage
    3 months ago

    The key clue is that it works in your local model file but goes blank only when the dashboard is connected to the deployed model. That points to the deployed semantic model's metadata being out of sync with what the report expects, rather than the DAX itself. Something changed around 11/21 - a deployment, a refresh, or a service update. To pin it down:

     

    - Diff the deployed model against your local file with Tabular Editor or DAX Studio. Compare the calculation group, its calculation items, and the calculated column that tags items as "Month"/"Quarter". If an item name or a tag value changed on the deployed copy, the slicer selection no longer matches and the item resolves to Blank.

    - Confirm the slicer's field (the grouping column) on the live-connected report still maps to the same column on the deployed model. A rename or redeploy can silently break that binding so the selection filters to nothing.

    - Check the calculation items still use SELECTEDMEASURE() and that calculation-group precedence didn't change.

    - If a deployment pipeline or an overwrite pushed a different version last week, redeploy your known-good local model and re-test.

    - Quick test: drop the grouping column and a simple measure like SELECTEDVALUE(Table[TagColumn]) onto the deployed-connected report to confirm the slicer selection is actually reaching the model. If that comes back Blank too, the binding/metadata is the problem, not the calc items.

     

    If you can share the calculation-item DAX and how the tag column is defined, it's easier to narrow down further.