![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
With all my experience in AS, the following are the two features I would love to see in it: 1. Properties for Calculated Members 2. "Default Set" - per dimension (Just like "default member") Thx |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Currently - there is no 'default set'. It picks two dimensions - one for row and one for columns. And the 'default set' for those two - is all the members of their first level - below 'All Level'. It picks the dimension highest in the aplhabet order... and then shows it on rows. And puts measures on the columns (analysis manager does that) Some browsing tools - pick the first two dimensions in an alphabetical order for rows and columns (Crystal) Some browsing tools pick time for the columns. And 'All level' of the dimension highest in the aplhabet order for rows... All this is too inconsistent. And third party tools make their own decisions... This is where I would love to have the control... Define what dimensions show up on rows and columns... and then - define - what members from each one of them show up as well... The idea of showing Time or Measures on columns by default is not bad... however... not always the best one. There are lots of properties for 'Dimension Type' and that's what the tools use... to display the defaults... however... It would be best if: 1. Define what dimensions are primary (by default on rows/ columns). Even this could be MDX driven 2. Define what's the default set for these two dimensions. (Easier if default set is only for the primary dimensions). The default set would get active when those dimensions are dragged onto rows and columns. Option to 'Aggregate' the defaultset when they are on the slicer. Or default on a seperate defaultmember when the dimension is on the slicer. |
#5
| |||
| |||
|
|
I would like to see a leaf level member be capable of rolling up to more than 1 parent in the same dimension hierarchy. This is a fairly common requirement in financial reporting scenarios that I have seen. |
|
I would also like to see improvemnts in the Writeback functionality. I would like to be able to writeback to local cubes. Role-based writeback would be useful as well so that I see writebacks that I have done whereas other people/roles only see writebacks that they have done if they have done any otherwise they see the true value as populated upon processing. |
#6
| |||
| |||
|
|
I would like to see a leaf level member be capable of rolling up to more than 1 parent in the same dimension hierarchy. This is a fairly common requirement in financial reporting scenarios that I have seen. |
![]() |
| Thread Tools | |
| Display Modes | |
| |