[Mondrian] Hiding measure values at certian dimension levels

[Anton Nikitin]

Julian,

Maybe you can find the following information useful in relation to the point
discussed.

We do support drill-through functionality for any correct MDX SELECT
statement (even if there are calculated members or multiple cells in it) in
our customized (non-rolap) Mondrian version. The idea is that at last
evaluation step it is known what data are "touched" by MDX statement. Then
it is possible to request from datasource all the underlying rows.

This behavior is different to MSAS and gives us some marketing benefits.

Anton

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Julian Hyde
Sent: Sunday, November 25, 2007 8:29 PM
To: mondrian at pentaho.org
Subject: RE: [Mondrian] Hiding measure values at certian dimension levels

Logged bug 1838148, "Allow drill-through from trivial calc members".

http://sourceforge.net/tracker/index.php?func=detail&aid=1838148&group_id=35
302&atid=414613

Julian

> -----Original Message-----
> From: mondrian-bounces at pentaho.org 
> [mailto:mondrian-bounces at pentaho.org] On Behalf Of Ognjen Milic
> Sent: Friday, November 23, 2007 3:47 PM
> To: julian at hydromatic.net; Mondrian developer mailing list
> Subject: Re: [Mondrian] Hiding measure values at certian 
> dimension levels
> 
> Julian Hyde wrote:
> >> Julian Hyde wrote:
> >>     
> >>> Third, could this be achieved using an existing mechanism 
> >>>       
> >> like calculated
> >>     
> >>> members, access control or format strings? Or perhaps 
> >>>       
> >> handled by the UI
> >>     
> >>> entirely?
> >>>
> >>>       
> >> Ognjen Milic wrote:
> >> I achieved this through format string expressions, but 
> then I loose 
> >> ability of drilling through in JPivot, because there is no 
> drilling 
> >> through for calculated members and
> >> no format string expressions for measures.
> >>     
> >
> > Suppose we could make trivial calculated members drillable. 
> Would that solve
> > your problem?
> >
> > I know people often create trivial calculated members just 
> to change format
> > strings, e.g.
> >
> > with member [Measures].[Foo] as ' [Measures].[Unit Sales], 
> FORMAT_STRING
> > ='$#,###.000' '
> > select {[Measures].[Foo]} 
> > ...
> >
> > Julian
> >
> > _______________________________________________
> > Mondrian mailing list
> > Mondrian at pentaho.org
> > http://lists.pentaho.org/mailman/listinfo/mondrian
> >
> >   
> Yes if  calculation of format string is not considered in 
> triviality of 
> calculated member. (If trivial calculated member can have 
> expression in 
> format string)
> 
> Ognjen
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
> 

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian