|
As it stands, Saiku 2.2 is not able to show the [All Member] and the [Members] together in a sensible way, for example:
The MDX generated is: I believe if the MDX is modified to: Union([Languages.Language].[All Languages], [Languages.Language].[Language].Members) The All Languages will show as an additional row, which will be more sensible. I think dragging the (All) level member to the Row or Column is a bit funny. When there is no other dimension in the Row/Column it serves as a place holder to completea the MDX. But when there are some other dimensions in the Row/Column, the All member is completely superfluous. It will just add another column that will have no bearing on the result (like what is shown in the diagram above). I believe a better approach is to make the UI a little like JPivot. We drag the dimension into Row/Column (rather than the (All) and/or Member), and when a dimension is already in Row/Column, the dimension will show two icons - a "+" icon for expanding the dimension (with the All member), and the looking glass icon for selecting individual member(s). We can probably have a third icon for expanding the dimension without the All member. Thanks for the great work. Best regards, chut |
|
The All member is indeed a bit funny. but you can disable it in your mondrian schema if you dont need/like it |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Tags:
Asked: 20 Jan, 10:25
Seen: 203 times
Last updated: 06 Feb, 04:26
Almost all business users that I have ever worked with are confused by the existence of the the ALL member in the dimension tree. This is exacerbated when there are multiple hierarchies in a dimension. If they need an aggregation of ALL, they would do that through other means like aggregating up to another dimension hierarchy (e.g. Month). I rarely see a need to list the ALL member in a view simply for label purposes.
I prefer that it is not shown in the object browser at all. The benefits of it being there are far outweighed by the awkwardness and confusion to users. Just my opinion.
yeah i agree marty. i dont know how it works in SSAS, but in mondrian the all member is an option for hierarchies... so in saiku we rely on the underlying OLAP engine to allow/disallow those ALL members...
Well, I do regularly use the All Member. For example listing the users with a All Users row as the the top or bottom as a summary row. Some of the measures are unique count aggregates, so there is no way to use the report engine to generate the All row.
Aggregating up anohter dimension hierarchy to me sounds more contrived than using the All member.
Anyway I came from Essbase background (cica 2000), where the All Member is always there. Essbase's Excel API is very simar to JPivot, where one drills down from the All member, but the All member is kept at the top.