Reply
Highlighted
Regular Visitor
Posts: 24
Registered: ‎01-23-2016
Accepted Solution

Make slicer dimension values dependant on related instances residing in (filtered) facts

I have a report with mulitple slicers. These slicers filter a measure called sales. I want the last slicer region to be dependant on the actual regions which exist in the sales after the sales is filtered by other slicers.

 

Dimension region

Dimension A

Dimension B

Fact Sales

 

So dimension A and B filter the fact sales, and the last slicer is region. For now it shows all regions but i only want the regions which are truly related to the residing sales. I do not want a solution which pertains the region inside the sales fact group I consider it unnecessary duplication. 


Accepted Solutions
Frequent Visitor
Posts: 6
Registered: ‎02-05-2016

Re: Make slicer dimension values dependant on related instances residing in (filtered) facts

Hi Giovi2008,

 

One way I use for exactly what you descibed is to do a calculated column with RELATED() in the sales data table that pulls the region. Then create the slicer with the region column just created. That way it would work as you described.

 

Another way you can test, is to set the relationship between the region dimension table and the sales table as both direction. 

 

Cheers.

View solution in original post


All Replies
Frequent Visitor
Posts: 6
Registered: ‎02-05-2016

Re: Make slicer dimension values dependant on related instances residing in (filtered) facts

Hi Giovi2008,

 

One way I use for exactly what you descibed is to do a calculated column with RELATED() in the sales data table that pulls the region. Then create the slicer with the region column just created. That way it would work as you described.

 

Another way you can test, is to set the relationship between the region dimension table and the sales table as both direction. 

 

Cheers.