Dependent filter affecting values in parent filter
When establishing a filter dependency hierarchy, it seems that the parent filters are affected by the child filters. For example, suppose I have data divided up into multiple "Projects" and some of those projects are then also divided into "Sub-projects". On my report I want to have a "Project" filter and a "Sub-project" filter. When I select a value for "Project", I want the "Sub-project" filter to populate with the available sub-projects for the selected project. However, if there are no sub-projects, then none should appear.
However, what I am actually seeing is that if a Project has no sub-projects, then the filter dependency is preventing those projects from appearing in the top-level filter at all. Essentially it seems as though the hierarchy is doing "inner joins" down the chain instead of "left joins". This doesn't seem right to me. What would be the reason to have a sub-filter control the available options in the parent filter?