Hey Glenn, Intriguing. I’ve tried the “callingPage=ClientView” params in the page include approach, but I’ve had to resort to using a model in the page include page to make use of the callingPage value. Have you had to use this method or another or another? I sorta like the nav bar approach with the CallingPage param. You’re using this instead of Master-Child pages? Seems not. From what I read it seems you’re using this for related lists on detail pages? I’m figuring a tab set with page includes in each tab that load after the initial page would provide that quickest initial page load along with providing a modular approach. Thoughts? With conditional rendering of columns and filters, Also, I don’t follow on the benefits of component that clones models from the parent page to the included page. What’s the use case here? Have you switched your product over to Master-Child pages?
