AggregationType.None - how should it work?

There is measure with the AggregationType None.

A cell with this measure is not empty only if coordinates in all dimensions are leaf. It's OK.

If the cube has fact dimension and for it dimension a leaf meber is selected, then it is clear, that cell values are build from only one fact table row. But AS doesn't realise it. Why? Is it a bug or it is by design?

My guess is that it is by design. I believe that the dimensions are treated equally with respect to the aggregation functions - hence all dimensions would have to be at the leaf level in order for a value to be returned for a measure that has aggregation function set to "None".

This does raise another question, however. What if the leaf level of the cube (measure group) is at a higher granularity than the fact table? How would the measure from the fact table aggregate up to this higher level of granularity, if the aggregation function is set to "None". I guess it is done with the sum function, but I have not tested this.

|||

"What if the leaf level of the cube (measure group) is at a higher granularity than the fact table?"

Then you have the SUM, as you guess :-)

And I think it is a bug or it was bad designed.
IMHO, the actual behavior of the AggregationType.None is unusable.

Could anybody controvert my opinion? What for nice solution can we build with actual implementation of AggregationType.None?

|||

Here are my observations from a previous post - but didn't yet receive confirmation from MS:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=616033&SiteID=1

>>

Deepak Puri

MVP

Posts 434

Answer Re: AggregateFunction -- Does "None" Work?

Edit Post | Delete Post(s) | Split Posts | Lock Post

Hi Dave,

The "None" aggregations seems to return a value if there's only a single fact record at that leaf of the measure group (SP1). I seem to recall back in the days of RTM that, if there were multiple fact records at a leaf, their "Sum" was returned, rather than null. However, this no longer worked when a fact dimension was configured.

Hopefully, someone from MS can corroborate this behavior - maybe it's by design?

>>