This seems to function fine if I drag customer and drop it on the detail button on the marks shelf of the 'users' sheet. Am I missing something?
Right, I know that will work, but I'm trying to avoid having thousands of marks on what is otherwise meant to be a simple "selection" interface. My actual data has hundreds of users and thousands of connected entities. Including customer on the detail shelf leads to hundreds of thousands of marks and slower performance.
Is there another way to get this to work?
It doesn't add any marks
EDIT: It doesn't add any visible marks, but I can understand how it would slow your calc down with a broader scope of data.
You're trying to build a many to many relationship here. In order to pass customer as a filter, it needs to be on the users sheet somehow;
I'll have a think about whether or not you can do it another way...
Not visibly, but it does behind the scenes:
With customer on the shelf, 11 marks; version without customer on the shelf has 4 marks (one for each userid). I know the difference between 4 and 11 is minor, but with my real data set, the difference would be massive--from a hundred or so to several hundreds of thousands.
Yep, I updated my comment just after posting r.e. visible marks.
Thanks for trying to work through this with me! Hate to make it sound like I'm not grateful for your efforts here.
But is there a way to do this without adding marks?
I didn't get that impression at all.
I'm going to noodle on it, but I really don't think so.
The users source either needs the customer in context or the customer_data sheet needs the user in context which would create a many to many on that source.
One possible approach would be to create your user summary without the customer in context, then create your second source as a live source connecting to your database. In your database you could have a view which creates the many to many on users / customers, but because you'll be filtering on user ID the scope of the data would be greatly reduced.
Would that be a possible option as far as your solution goes?
Sadly, no. We can't have live connections to our database.
Sounds like there's no way out of having customer IDs in the detail?