Fix and enhance Data Table relations

request for Fix and Enhancement.

As an analysis developer I would like to have more control on Data Table relations and how they react to my filtering and range setting because the current implementation is not working as expected.

Unexpected behavior

Data Table relations do not cascade down from other relations when having multiple in-between tables. The "Include filtered rows" option to me should be more of a "Include filtered range only" option as it is working now.

Abstract of the problem:

I have two tables that I use to limit data in a main table 'Plays' then there is an intermediate Date Table called 'Plays PXR' towards Data Table 'Cross Lines' using two relations. Attached is a picture of the set-up.

When I set the filter relations as described in the picture and filter in both external Data Tables on the Play_ID (External1 Play_ID 3.00 - 10.00 AND External2 Play_ID: 0.00 - 7.00)  without setting a filter on Plays I'd expect the rows would be filtered out in Plays by the two external tables (logic AND as displayed by the blue bar inside the filter range).

This appears to be happening and also cascading down to Plays PXR, however when marking data in the Plays PXR I'd expect the combination of Region_ID: A and Product_ID: Y to be filtered out towards the Cross Lines Data Table. 

Cross Lines is displaying the aforementioned combination as data rows still present. This can be visualized by selecting all rows in Plays PXR seeing rows are not marked in the Cross Lines table.

Filtering to the range set in the External tables on the Plays Data Table the data is also limited in Cross Lines.

Conclusion 

This is why I feel the 'filtered rows' feel more like a 'filtered range' to me. There is something to say to probably have both methods available still after fixing. 

Attached is the situation when filtered in both external tables.