I have a Crowd bizobj that identifies a user specified group of people. Various other reports and business objects would benefit from adding the Crowd to act on variable groups. I've done view-within-a-view before and it works, but in those cases, the subordinate view is part of the same business object, so it always has control over both views.

What's the best way to incorporate a view_crowd into an Invoices object? Adding the Invoice view to the Crowd object works, but spreads Crowds across the application and loses its cohesion. Adding the view_crowd to the Invoice object means replicating Crowd's selection interface. Adding a Crowd bizobj to Invoice and every other object that wants it seems like overkill. Which of the three ideas, or is there a fourth, should I use?

Chris.