I am creating a calculated member in a dimension from two "regular"
members - e.g. A + B = C. My desire is to only show the calculated
member (i.e. C) and hide the regular members (i.e. A and B).

I tried using the security roles that are part of the cube to do this.
It seems to hide the calculated member when I choose to hide the
regular members only. When I show both regular members, the
calculated member shows just fine.

Is there a way to accomplish this? Is MDX a possibility?

Thanks, Chris

Look in the advanced properties of the measure. There is a "Visible"
property. Set it to false.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chris" <chris_is_way_cool (AT) hotmail (DOT) com> wrote

Hi Dave,

I tried setting the "Visibe" property to false too. Once I make the
regular members not visible, the calculated member fails. So, I am
still stuck.

Thanks, Chris

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

That just confirms my original believe - that you cannot do this in AS...

You need to something in your relational environment....you need to put in a
"father" dimension - if snowflake
in a new table.

Of course its another type of aggregation than the normal one because you
don't want to see the lowest level - so could it be:

facttable --> reference a and b in a dim table --> this dim table references
another table with c for a and b and then the "normal" value for the rest

Then you choose to disable the lowest level in cube editor so that only the
new semi-aggregated level is shown.

/Michael V.

"Chris" <chris_is_way_cool (AT) hotmail (DOT) com> wrote

Chris did you hide regular measures or regular members ? What exactly fails
about calculated member ? This scenario should work, and it works fine for
me in Foodmart.
--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

So it can be done ?

I'm a little confused....is it specific dimension members in one dimension
that is bundled up into one dimension member in
the same dimension as a calcluated dimension member on that dimension ?

What step do you need to go through ?

a) calc dim member in as - what would syntax be ?
b) security roles settings afterwards

Mostly confused about a).

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

members can refer to hidden members, but cannot refer to secured members.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

But you can use this to hide specific members - lets say I have a
dimension A with members A-1-1 and A-1-2 and I can make a calculated member
A-1 and
then hide A-1-1 and A-1-2 ?

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

As Mosha said, it depends on in what context you are hiding things.

If for *all* users, then you can hide complete cubes, dimensions, levels,
measures, or member properties from end users who browse cubes with client
applications. The visibility of these objects is controlled by the Visible
property. For more information, see Properties Pane (Cube Editor Data View)
and Properties Pane (Dimension Editor Data View). Likewise for *all* users,
you can use the "Hide Member If" property in the Dimension Editor to expose
a ragged hierarchy -- by hiding some members.

If you are hiding members for only certain users then this is what Mosha
called "secured members".

Does that answer your question?
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Michael Vardinghus" <michaelvardinghus (AT) hotmail (DOT) com> wrote

Yes thanks

Are there any significant performance implications in using Secured members
?


"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote