problem with drillthrough and relationships (cardinality)

[DenBI]

I can't get my head around an issue. I have two tables with data, one containing slotreport data (high level data), and on containing slotdetails data (fine grain data) containing more details about the slots. tables are related through a slot(id) but as in both tables keys are not unique I use a connectiontable and set up relations between the tables, based on the slotID's. as a result I get a many (slotreport) to one (slotid) to many (slotdetails) relation chain. (see picture)

for some reason I can't use drilltrhough on the slotid's from the slotreport table in order to get slotdetails data in my details tab. I would expect that since these tables are logically related PBI would understand then when using a key from one table, it could be used in drill though on another related table. Am I doing somehing wrong?

Unfortunately I can't include .pbix, so please find attached some photo's to illustrate.

Hooe someone can help....

[v-yuta-msft]

Hi DenBI ,

Set the direction of relationship between slotreport and slotID to be bidirectional direction and check if the issue still occurs.

Regards,

Jimmy Tao

[Seward12533]

Hard to tell from what you provided but try one of these.  Dealing with multiple fact tables can get a bit tricky. 

1. Filter on Slot from your Bidge Table this will force the filter down into both tables. 
2. IF you need to filter on somethign else then you can set the relationship between the bridge Table (SlotIDs) and the SlotReport table Bidirectional. This will force the filter to flow back up and then down into the other table.
3. You can use a trick to force the filter context by writing a measure for the slotdetail data that explicitly references the SlotReport table by specifying the table name within a calcualte.  (see some screen shots below)