Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Unable to cross-filter table

Hi Community Champs,

I am attaching the file (https://drive.google.com/file/d/1cYACKgoQDBE1WNV0UWeGHBm4zeavywvV/view?usp=sharing)- if somebody can show how the request below needs to be accomplished- it would be great.

 

The ask is to be able to filter the table in green based on the group selected in red.

Currently, it gets filtered only if I drill down DaysAwayGroup & select an employee ID but not based on sub-totals for each group. For eg: If I select 180+ category- it should just show me records for those 3 employees IDs alone- but it doesn't

 

Need Help
  • daxer-almighty's avatar
    daxer-almighty
    5 years ago

    Anonymous 

     

    Yes, this problem is not for the faint of heart 🙂 I've solved it but don't have time right now or even willingness to discuss the solution. If you have questions about it, please post it here and I'll reply later. The model into which I transformed yours is not totally perfect only because I didn't know all the meanings of the fields, so there might be dimensions that don't have all the relevant attributes or have attributes that should belong to other dimensions. In general, fact tables' fields should not be exposed in the UI, they should always be hidden. I could have achieved this by moving some fields (especially the dates) into the Flight Attributes dimension or by creating suitable measures (since you're not likely to slice the data by the start and end dates, anyway). I leave this all to you. The initial model you had was bad for many more reasons that I would like to talk about. Please always stick to the star schema if you don't want to have problems you'll be scratching your head about for days or weeks.

     

    And here's the solution.

2 Replies

  • daxer-almighty's avatar
    daxer-almighty
    Icon for Solution Sage rankSolution Sage
    5 years ago

    Anonymous 

     

    Yes, this problem is not for the faint of heart 🙂 I've solved it but don't have time right now or even willingness to discuss the solution. If you have questions about it, please post it here and I'll reply later. The model into which I transformed yours is not totally perfect only because I didn't know all the meanings of the fields, so there might be dimensions that don't have all the relevant attributes or have attributes that should belong to other dimensions. In general, fact tables' fields should not be exposed in the UI, they should always be hidden. I could have achieved this by moving some fields (especially the dates) into the Flight Attributes dimension or by creating suitable measures (since you're not likely to slice the data by the start and end dates, anyway). I leave this all to you. The initial model you had was bad for many more reasons that I would like to talk about. Please always stick to the star schema if you don't want to have problems you'll be scratching your head about for days or weeks.

     

    And here's the solution.