Here is a common scenario, where you may have 2 main data tables, then a single “join” table that is a child of both. In the attached sample app, you see the scenario of product and order, with the join table being line_item. In the join table, there is a reference to a product record, as well as an order record, amongst other data such as quantity.
Here is the backend data
The Detail views for both parent tables will show an inline view of “Related line_items”. However there is no “natural” way to show a different inline view depending on which parent table the user is in. Consider that from product, you’d want to see [order] and [qty] columns, but from order, you’d want to see [product] and [qty] columns.
The way to accomplish this is to start by creating a new slice for line_item table.
Just a basic slice, include all columns, include same permissions, do not include a row filter condition.
Next, in one of the parent tables (I chose product), create a new Virtual Column. You’ll copy the REF_ROWS() expression from the existing “Related…” VC, and simply change the table name to the name of the new slice.
REF_ROWS("new slice name" , "ref-column" )
You can find the sample app “Differing Inline Views” on my portfolio, here: