1 of 1 people found this helpful
Please find the attached as an example of
how this scenario could be implemented in Tableau.
It is the actual [Customer Name] Dimension values
that should be sent from one view to another via Filter Actions.
So the [Customer Name] Dimension should be present (on Details)
on every Source view used in the Filter Action(s).
Users should be able to multi-select a group of Marks (Customers) on a view in a single gesture.
This could be done when selecting the [Region] Header(s) -- not the actual Marks,
as they're on top of each other (with the Stack Marks set to OFF).
So each view should have [Region] Headers visible (hence clickable),
and users should be trained to the Header selection behaviour.
Besides, Filter Actions for the 1st and subsequent views
could be made a little bit differently (as in the example) -- depends on a case.
Hope it would be of some help.
Thank you very much Yuriy. With these instructions and your example I was eventually able to getting it working correctly.
Still, I can't help thinking there must be a better way to do it. With a large amount of data the current approach is painfully slow, although maybe that's unavoidable.
If the # Customers is high, so the Customer on Details could be a performance hit,
then there would be alternatives -- as 'simple' as a table with all paths available in the data
(or even all theoretically possible ones) with the aggregated Customer CountD as a Measure.
Please find the attached w/mod on Sheet 7.
I finally got some time to take a look and implement this solution.
It works well, and is much better performance-wise than the other solution. I think once I play around with some filters etc. I can make it much more useful too.
Thanks for your help!
Robert, you're welcome.