Forum Discussion

neatmachine's avatar
neatmachine
Microsoft Employee
5 years ago
Solved

Slicer values missing in embedded report with filter

Hello,

 

I've run into an issue with my embedded report. Whenever I include a filter in the query parameters, my slicer values disappear.

 

Ex:

 

I have a chart and three slices on fields X, Y, Z. I've embedded a report with the query param '&filter=table/fieldQ = 3'. Field Q is not fields X, Y, or Z in my slicers. The data in fields X, Y, and Z are also not restricted by the filter on Q (nor is this behavior the same on PowerBI Desktop for the same filtered value)

 

Has anyone run into this? Does using a filter in the query string of an embedded report disable all slicers?

  • Well...I found the issue.

     

    My slicers each had their own filters on an individual value. I just needed to clear them.

     

    Apparently the relationship(s) between slicers and filters differ in some way(s) between embedded and non-embedded reports, since the behavior was different between the two.

3 Replies

  • neatmachine's avatar
    neatmachine
    Microsoft Employee

    Well...I found the issue.

     

    My slicers each had their own filters on an individual value. I just needed to clear them.

     

    Apparently the relationship(s) between slicers and filters differ in some way(s) between embedded and non-embedded reports, since the behavior was different between the two.

  • Hi neatmachine 

     

    Could this be happening because there is no value for the value Q

     

    So the slicer does not show any values because of what is set in the query parameter?

    • neatmachine's avatar
      neatmachine
      Microsoft Employee

      Hello, thanks for the tip!

       

      Unfortunately this doesn't appear to be the issue. The chart itself has data for the filtered value, and that data matches what I see when I filter the report locally/not-embedded. The only difference is that the embedded report loses the slicer values (the server/local report does not).

       

      The query param looks like this:

       

       &filter=Table/Field eq 27745138