Forum Discussion

RMRaptor's avatar
RMRaptor
Frequent Visitor
3 years ago

Filter Detail table based on Master Table- Data slicer selection

Hello All 

Master-Detail table are connected by Employee Id key 

Master table  show list of all projects and employees , when employee is selected from master matrix table, detail matrix table gets filtered  for specific employee and show all projects that employee is working.  In Report page i have date slicer from master table which is filtered to show 2023 year projects, so how do i pass same date slicer filter selection to detail table .?

do i have to create second relationship on date column, in that case secon relationship will be optional not as primary , what  are options.?

Thanks

RM

 

1 Reply

  • Hi RMRaptor,

     

    By default, filters can only flow down active relationship paths. Since your tables are connected strictly via Employee ID, your date slicer on the Master table has no pathway to pass its filters to the Detail table.

     

    ​Here are the three ways to fix this, ranked from best practice to quickest workaround:

     

    ​1. Use a Shared Date Table

    ​Decouple time from your data tables by creating a centralized Calendar table.

    • ​Connect a new DimDate table to both Master[BeginDate] and Detail[Month] via active 1-to-Many relationships.
    • ​Move your report page slicer to the new DimDate[Date] column. It will now simultaneously filter both tables cleanly.

    ​2. Use an Inactive Relationship via DAX 

    ​If you cannot add a new table, create a direct relationship between your date columns and activate it programmatically.

    • Build a relationship between Master[BeginDate] and Detail[Month]
    • Write your visual calculations as explicit DAX measures using USERELATIONSHIP

    3. Enable Bi-Directional Filtering

    If you need a quick drag-and-drop fix without altering data structures or writing DAX:

    • Double-click your existing Employee ID relationship line and change the Cross filter direction from Single to Both

    But RMRaptor - please remember bi-directional paths can sometimes cause query ambiguity or degrade visual rendering performance

     

    Let me know if this helps!