Have you connected these tables using references?
If so, then inside the Teams table you should have:
- Related Activities
- Related Objectives
Also, inside Objectives, you should have:
If so, then you’ve got inline views for these - I assume is what you mean by:
I see what you’re talking about: both would share the same inline view.
You want to know how you can have one inline view for one view, and another for another.
The answer is… complicated, but doable.
Perhaps there’s a way to use CONTEXT() here, but what I’ve done in the past is:
- Create a slice of the table I want another view for
- Make my view for the slice
- Create an additional column in my parent table, using a variant of the Ref_Rows(“Table”, “Ref_Column”) that’s already there. Instead of pulling records from the original “Table”, instead switch that to the slice you just made: Ref_Rows(“Slice”, “Ref_Column”)
- Specify which column to show in your parent detail views.
This creates another inline view (just like the one that’s already there) but the data comes from the slice (which has it’s own view) - thus giving you the ability to change how records are shown in one view from the other.
Complicated, yeah… maybe a bit messy. I’m wondering if you might be able to use CONTEXT() to determine which inline view would be used for child records on a parent detail view… I’ll experiment and report back.
******UPDATE - I tried creating a duplicate inline view and using CONTEXT(“View”) <> “ViewName” to exclude one and show the other… failure.
Did not work. But honestly, that would be asking a lot of the system - to evaluate not only if the column should be shown, but also which view to use?