I have a cube which has multiple fact tables, with different granularity.

One of the fact tables is Price, which is by Product, Geography and Time,
but for example does not have Customer (as the other fact tables). Everything
works fine, I can display data from all fact tables.

But I don't want the Prices to be aggregated in any of the
dimenions/hierarchies. I want the Price to be displayed, just at the lowest
level of each dimension.

I changed the "Aggregation Function" property for the Meausure Price to be
"None", but after I do that, the data is not available in any level of my
hierarchies, including the lowest level.

I checked some books, searched online, but no luck. It seems that I'm doing
the right thing, but it is not working. What am I doing wrong?

If I set the "Aggregate Function" property to be "SUM" (it's the default),
I can see the right data in the lowest level, but also the aggregated data in
higher levels. Which I don't want..

Please help!!!! Thanks.

Ercilia

Here is a thought:

Can you define Price as an attribute (property) of Product? Instead of
having it defined as a measure, since you don't want to aggregate it, can you
define it as an attribute and property of let's say, the product dimension?

SHW

"Sampa2870" wrote:

I don't think so, because the Price measure is dimensioned by Product,
Geography and Time.

The question I have is why is not behaving as it suppose to. Is it a bug?

"SHW" wrote:

We have the same issue here with a value that was only meaningful on certain
level. On the day level it made sense, but on a monthly level it didn't. It
only confused and mislead the users when they saw it on the monthly level.

There is a property for MeasureExpression. I'm guessing some MDX would give
you what you're looking for and most likely the IsLeaf function.

Try this:

http://www.databasejournal.com/featu...le.php/3633696





"Sampa2870" <Sampa2870 (AT) discussions (DOT) microsoft.com> wrote

We had the same issue. To resolve it, we found 2 solutions :
1. If you just want to see your measure at the bottom level, you can
hide your measure, and define a calculated member to show it, testing
the level
2. In our case, we wanted to have a average of the price, so we don't
have a measure with the price. We just have the amount of sales, and
the quantities, and we have a calculated member to show the average
price, dividing amount by quantities. At the bottom levels, you have
the real price of your product, but at aggregated levels, you have the
average...


Good luck.

Thierry


Jesse O. a écrit :