Hey ​@Matthias Danneel,

What do you mean by don’t work?
I think I follow, but would you further describe the example of your “hierarchy levels”? 

Do you mean that the dropdowns do not get dynamically filtered based on previously selected filters?

Mike, Consultant @ Automatic Nation 
YouTube Channel

Hey ​@Mike_AutomaticN ,

In my case the three hierachies would be Customer, Project and Resource (all with their own tables and linked to each other). In my list-interface I have a hierarchy with Customer the highest, then projects and then resources. 

When I collapse everything right now and select on projects that are for example ‘Status = Pipeline’, all customers stay in the list even if they don’t have projects that are in status = Pipeline. I have to manually click open each customer and check if they have a project like that but this defeats the use of the filter…

Kind regards,

Matthias

Hey ​@Matthias Danneel,

It can take some experimenting to get the hierarchies and filters to behave how you want them, however two things I think may help here:

(1) Enable the ‘Hide sections with no additional rows’ toggle. At the page level (i.e. the whole page is blue bordered, not just your list view), inside the Levels (hierarchy) control, right at the bottom. It has moved around over the years, in case you were used to seeing this control back out inside the list view.

(2) Prior to ‘filters at every hierarchy level’ we used to do ‘lookup cascades’, i.e. pass the relevant fields all the way down to the lowest level. Then you just base your page on that lowest level table, and filter like normal. This still works & is a fine alternative, especially if it’s only a few fields you’re passing down and don’t expect that to change much.