Is there an MDX function thats ignore the relative cell refferanc

[Wei Lu [MSFT]]

Hello Knut,

Basically, we could not just drilldown for the benchmark value only on 2
dimensions.

I would like to know this issue more detailed so that I can provide some
further assistance.

Could you post some sample schema of your cube and let me know what's
result you want.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Knut Ivar]

This calculation summarize the biomass for an region - even if the client
user does drill down many levels in the "RegionProducer".

CREATE MEMBER CURRENTCUBE.[MEASURES].bmRegionBiomassPeriod
AS
sum(Ancestor([Producer].[RegionProducer].currentmember,[Producer].[RegionProducer].[Region]),[Measures].[Biomass]),
VISIBLE = 1;

Thats fine. But if the client users add more dimensions to the olap viewer
this benchmark value will be splitted on the new dimensions that the usere
add. Example they add WeightClass 0-5kg,5-20kg and 20+ the benchmark values
should be the same for all the classes. It should not matter. Its important
that the benchmark value don't changes when users add other dimensions. My
customers will be realy confuced if the Regional bencmark values changes when
they add other dimensions to the cubebrowser.


So I would like to add and an statement to the MDX-statement thats tell the
command that it should ignore the rellative possision when it calculate, an
only use the rellative possision to get the input parrameters for the
calculation. Maybe some thing like the LOOKUPCUBE() command, but in the same
cube... I have not experimented with the LOOKUPCUBE command at all, but I
think it is an command for looking up values in other cubes.

I would like to have an command that says "drillUpTopMyCube" - and then
just add the month dimensions in my calculation, then I would have the
benchmark value I am looking for.

Thanks
Knut Ivar

Post by Wei Lu [MSFT]
Hello Knut,
Basically, we could not just drilldown for the benchmark value only on 2
dimensions.
I would like to know this issue more detailed so that I can provide some
further assistance.
Could you post some sample schema of your cube and let me know what's
result you want.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Wei Lu [MSFT]]

Hello Knut

If you add the WeightClass dimention, it makes sense that it will aggregate
the benchmark on that dimention so your client will see the benchmark value
will changes.

This makes sense since when you add a dimention, you wants to drill down
the dimension to see the detailed value.

I am not aware of the bussiness logical of your project so could you please
post the schema of the detailed data source table of your cube and let me
know some detailed information of your cube?

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Wei Lu [MSFT]]

Hi ,

How is everything going? Please feel free to let me know if you need any
assistance.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.