Thx for your reply. But it is not that easy how it looks like
I still want to show all Segments and Years on Details, even if they are empty for these products. At the end it should show me only these products, and all possible Years and Segment for whole data set.
So you want to send Product IDs from aggr to details view --
though there is no [Product ID] pill on the aggr.
Then you have to have an intermediate view --
where [Product ID] dim pill is on Details --
and have a visible (and clickable) object
to send all filtered Product IDs at once.
So it should be a Header, not a Mark.
Please find the attached as an example.
The layout is (blatantly) called "Header-as-Button".
example_YF.twbx 1.3 MB
Ok. Let's do it with Product ID on aggr view.
How to combine all IDs into one mark and send it to Details? I've tried different ways, but without success:
- Create list of IDs in tooltip. In this case i should select multiple marks and use Menu action, again not with Select
- Create calculated dimension and put it on both views with FIXED function, but products can be sold in different segments and years
Another option would be a self-join on [Product ID] --
if you don't mind about the resulting dataset size.
If size matters, it is an advice of making an extract first,
then doing a self-join (without extracting the result set).
Please find the attached.
X-example_YF.twbx 1.6 MB
Nice. But the data size is matter. Also it doesn't work with published data source
Is it possible to do it with LOD and Table Calcs on columns? I'm still thinking it is doeble...
1 of 1 people found this helpful
If there is any other way, I'm afraid I'm not aware of it, sorry.
Regarding the Self-Join result size and performance, I suggest you to
1) Prepare an Extract from the original (aggr) DS, keep this *.TDE file.
2) Make a new (details) DS using the (self-joined) Extract from step 1.
This step would require the Extract *.TDE file to be available locally.
3) Publish the DS (from the step 2 above) on TS for users to connect to.
When on a dashboard, one could be using the resulting (details) DS
on the details (target) view only, while the aggr (source) view
would come from the original DS (live or extract -- you decide).
Filter Action from the Source DS to the Target DS --
with the Exclude when un-selected -- would do the rest.
Thank you for both cases. We chose first way With extra button.
So my idea is that:
- Have product id in details for aggregated view. Then we can use table calculation to count marks and show total count only for FIRST()=0 mark and hide null marks
- Then have a calculated dimension for each crossing cell - Category, Year, Segment. So it will return result only for Products in that cell on ID level. so it should not hide Years and Segments
- Use action filter to pass that dimension to rows in target worksheet
But seems it is impossible...
Glad it helps (one way or another).
As for your recent ideas,
I have no idea about the point #2.
For me the problem is to find a simple way
to pass a vector of dim values (Product IDs)
from the (very) original Source view to the Target one.
By the nature of Filter Actions it should be a multi-select,
so one have to select several Marks at once (not a just single Mark).
This is what my first ("Header-as-Button") approach essentially does.
This would be the reason why your point #1 could fail.
Leaving just a single Mark per Category / Segment / Year
one couldn't do a multi-select, so only one Product ID is selected.
Besides, sending other dimension values makes all the thing a no-sense --
one can do this easily from the original aggr Source view.
Another way of doing a multi-select
is filtering on a many-to-many (joined) table.
This is how my second dash (the X-one) is made.
I couldn't imagine the third one.
If I could, I would let you know immediately.