Forum Discussion

YouCanCallMeAl's avatar
YouCanCallMeAl
Frequent Visitor
2 years ago

Compare data from one table by multiple slicers

Dear Community,

I would like to compare data in a matrix visual that is present in one table by the use of multiple slicers.

 

The table is structured like

DomainVariantIDTagPrice-APrice-B
D2V2ID1T2123,3432423,1
D1V2ID4T1232,234324,33
D5V4ID4T223324,1324
D4V3ID5T12344553,9
D2V1ID2T345645,23345,55
...     

 

I would like to compare variants by slicers:

  • Slicer A -> (multi)select out of column "Variant"
  • Slicer B -> independent (multi)select out of same column "Variant"

 

Compare the scenarios in a shared matrix visual:

 

Rows: 

Domain

 + Variant
   + ID
     + Tag

 

Values (in columns) based on Slicer A:

  • Price-A
  • Price-B

Values (in columns) based on Slicer B:

  • Price-A
  • Price-B

Delta Values (Delta between the 2 sliced Values)

  • Price-A (Slicer A) minus Price A (Slicer B)
  • Price-B (Slicer A) minus Price B (Slicer B)

 

Goal is to filter the Variant based on the 2 slicers and to compare them.

 

Attached is the pbix example where I started to work with. The red x mark the visuals that do not work yet.

 

PBIX Download 

 

 

Would be glad if I can get some help.

5 Replies

  • What exactly are you trying to compare?  Is that something your users can do by themselves when you give them the power to use custom filters (and "personalize visuals") ?

    • YouCanCallMeAl's avatar
      YouCanCallMeAl
      Frequent Visitor

      Thanks for your feedback lbendlin 

      I just revised my post and added a sketch.

      Yes, the user shall be able to set the slicers and the result is shown in one matrix visual. So that we are able to compare within the same structure.

      The Prices shall be comparable wihin their category, so

      • Price A (based on Slicer A) compared to Price A (based on Slicer B)
      • Price B (based on Slicer A) compared to Price B (based on Slicer B)
      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User

        Consider loading your table twice, and then use independent slicers.  Anything else will be hard to maintain.