Forum Discussion

jmunn's avatar
jmunn
Icon for Advocate I rankAdvocate I
1 year ago
Solved

Help with table relationships and filter propagation

Hi, I have been wrestling with a filtering issue that I can't seem to solve, and I haven't been able to find the answer in other posts I've read, so posting for advice here...   I have the followin...
  • v-pnaroju-msft's avatar
    1 year ago

    Thank you, lbendlin , for your response.


    Hi jmunn,

    We appreciate your inquiry through the Microsoft Fabric Community Forum.

    Based on my understanding, it appears that the filter context from Tables A to C is not fully reaching Table E due to either the direction of relationships, inactive links, or filtering limitations in your data model.

    Please follow the steps below, which may help to resolve the issue:

    1. Ensure that there is an active one-to-many relationship from Table D (Students) to Table E (Assessments).
    2. Filters should flow from Tables A to B to C to D to E. You may need to set bi-directional filtering between the intermediate tables with caution.
    3. Confirm that no inactive or ambiguous relationships exist. Remove any unnecessary links that may obstruct the flow of filters.
    4. The slicers work when a specific Student ID is selected, indicating that the context is not reaching Table E globally. Ensure that the slicers and visuals are not overriding this context.
    5. Keep student and course information in dimension tables, with assessments as your fact table, to ensure effective and clear filtering.

    If you find our response helpful, kindly mark it as the accepted solution and provide your feedback. This will assist other community members facing similar queries.

    Thank you.

  • jmunn's avatar
    jmunn
    1 year ago

    Thanks v-pnaroju-msft very much for these thorough and specific suggestions.

     

    I've gone through each of them, and in the course of doing so discovered that the incorrect filter propagation was actually an issue with blanks.

     

    Table D doesn't have any blanks the field being used in the relationships with other tables, but there can be values in Table B or Table C that don't exist in Table D. It seems that, when this happens, a blank is somehow introduced, which then interferes with the expected # of records coming from Table E. I don't totally understand how this happens, but I added a "Filter on all pages" to filter out blanks in Table D, and that seems to have solved the issue. 

     

    Again, thank you for the nudge and assistance!