Cascading from different tables is not working

[Anonymous]

Hello, 

I have a source table Time and I have created 3 tables (Region, Market, and Product) out of Time Source because I need to show these 3 columns in the slicer in "descending order" based on numeric Actual value (which I couldn't do it on Time table as there are multiple data present for 1 dimension and aggregation is a problem) 

Region_Slicer = SUMMARIZE('Time','Time'[Region],"Act(RP)",sum('Time'[Actual(Rp)]))

Market_Slicer = SUMMARIZE('Time','Time'[Market],"Act(RP)",sum('Time'[Actual(Rp)]))

Product_Slicer = SUMMARIZE('Time','Time'[Product],"Act(RP)",sum('Time'[Actual(Rp)])) 

Now I have joined these tables with Time Source table based on their dimension field and as shown in the picture.

All the Slicers are sorting descending based on Actual(RP)

Problem is when I am selecting any value from the slicer only Time Source Tables values are getting affected and none others. e.g. when I select a Region from Region Slicer, Values in Market and Product Slicer remains unchanged.

This is how my slicers look like in report

Am I doing something wrong? Could you help?

Thanks

[v-yuta-msft]

@Anonymous ,

All you have done is correct, but the three dimension tables doesn't have relationship with each other, so when you select a region from Region_Slicer, you can only filter the fact table, not other dimension tables(slicer tables).

In addtion, in this senario, you also can't build relationship between the three dimension tables because it may cause ambiguous error.

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

But it is not solving my purpose. I need to filter other dimensions as well based on each other.

Any suggestion on how this can be achieved?

[v-yuta-msft]

@Anonymous ,

You can build one-one relationship between Dimension table1 and Dimension table2, Dimension table2 and Dimension table3, then build one-many relationship between Dimension table3 and fact table.

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

I can do that but on what column? because as soon as I'll add one more index column for 1:1 relationship my sorting based on numeric field Actuals will not work.