Drilling down brings back incorrect numbers

do you have partitions or calculation around this measure?

I suffer the same issue with partitionned cube where , in fact, I have a
"conflict" between 2 dimensions.
SSAS auto assign the slice of the cube for a partition, in my case I have 2
years level in 2 different dimensions, so SSAS detect correctly the
partition at this level.
but I have a month of my time dimension which appeared in another year in
the second dimension (sometimes the combination result in the right year,
sometimes not); SSAS will produce unexpected behavior in this setup because
SSAS take the aggregate value in 1 place or in the second place "randomly".
A simple refresh in the pivottable change the numbers displayed!
and forcing the slice of the cube raise an error during the aggregation
process step due to the conflict.
to solve the issue in my case I have to insure that there is no conflict in
the partition and slices.

"Jesse O." wrote in message
news:eGkSvUSXHHA.3980@TK2MSFTNGP02.phx.gbl...
> I've had a weird issue when drilling down into a dimension. For the life
> of me I can't figure out what's going on.
>
> The cube has two dimensions - Date and Region. Region has two levels.
>
> For example:
>
> When looking at the top level total, Region 1 comes back as having 15,000.
> However when drilling down into Region 1, the number only returns 10,000
> as a total.
>
> Where are those other 5,000? It is incorrect across the entire dimension.
>
>
>

good to know im not crazy!

how do you ensre there is no conflict between the partitions and slices?


"Jeje" wrote in message
news:9721AC07-71B8-43A8-82A3-022CB586E147@microsoft.com...
> do you have partitions or calculation around this measure?
>
> I suffer the same issue with partitionned cube where , in fact, I have a
> "conflict" between 2 dimensions.
> SSAS auto assign the slice of the cube for a partition, in my case I have
> 2 years level in 2 different dimensions, so SSAS detect correctly the
> partition at this level.
> but I have a month of my time dimension which appeared in another year in
> the second dimension (sometimes the combination result in the right year,
> sometimes not); SSAS will produce unexpected behavior in this setup
> because SSAS take the aggregate value in 1 place or in the second place
> "randomly".
> A simple refresh in the pivottable change the numbers displayed!
> and forcing the slice of the cube raise an error during the aggregation
> process step due to the conflict.
> to solve the issue in my case I have to insure that there is no conflict
> in the partition and slices.
>
> "Jesse O." wrote in message
> news:eGkSvUSXHHA.3980@TK2MSFTNGP02.phx.gbl...
>> I've had a weird issue when drilling down into a dimension. For the life
>> of me I can't figure out what's going on.
>>
>> The cube has two dimensions - Date and Region. Region has two levels.
>>
>> For example:
>>
>> When looking at the top level total, Region 1 comes back as having
>> 15,000. However when drilling down into Region 1, the number only returns
>> 10,000 as a total.
>>
>> Where are those other 5,000? It is incorrect across the entire dimension.
>>
>>
>>

well...

I have found this when I setup the slice, SSAS refuse to do a processindex
due to the conflict.
but the system don't display the real reason.
So I play with the cube and I have found the moving month issue
I have not tested this with the SP2, so maybe there is some changes here.



"Jesse O." wrote in message
news:OgsvsIWXHHA.1216@TK2MSFTNGP03.phx.gbl...
> good to know im not crazy!
>
> how do you ensre there is no conflict between the partitions and slices?
>
>
> "Jeje" wrote in message
> news:9721AC07-71B8-43A8-82A3-022CB586E147@microsoft.com...
>> do you have partitions or calculation around this measure?
>>
>> I suffer the same issue with partitionned cube where , in fact, I have a
>> "conflict" between 2 dimensions.
>> SSAS auto assign the slice of the cube for a partition, in my case I have
>> 2 years level in 2 different dimensions, so SSAS detect correctly the
>> partition at this level.
>> but I have a month of my time dimension which appeared in another year in
>> the second dimension (sometimes the combination result in the right year,
>> sometimes not); SSAS will produce unexpected behavior in this setup
>> because SSAS take the aggregate value in 1 place or in the second place
>> "randomly".
>> A simple refresh in the pivottable change the numbers displayed!
>> and forcing the slice of the cube raise an error during the aggregation
>> process step due to the conflict.
>> to solve the issue in my case I have to insure that there is no conflict
>> in the partition and slices.
>>
>> "Jesse O." wrote in message
>> news:eGkSvUSXHHA.3980@TK2MSFTNGP02.phx.gbl...
>>> I've had a weird issue when drilling down into a dimension. For the life
>>> of me I can't figure out what's going on.
>>>
>>> The cube has two dimensions - Date and Region. Region has two levels.
>>>
>>> For example:
>>>
>>> When looking at the top level total, Region 1 comes back as having
>>> 15,000. However when drilling down into Region 1, the number only
>>> returns 10,000 as a total.
>>>
>>> Where are those other 5,000? It is incorrect across the entire
>>> dimension.
>>>
>>>
>>>
>
>

Could it be unknown member hidden issue?

"Jesse O." wrote:

> I've had a weird issue when drilling down into a dimension. For the life of
> me I can't figure out what's going on.
>
> The cube has two dimensions - Date and Region. Region has two levels.
>
> For example:
>
> When looking at the top level total, Region 1 comes back as having 15,000.
> However when drilling down into Region 1, the number only returns 10,000 as
> a total.
>
> Where are those other 5,000? It is incorrect across the entire dimension.
>
>
>
>

I don't believe so.

All unknowns are taken care of at the database level...


"yongli" wrote in message
news:C7C4F988-4D0D-4AF5-927E-4013AB89FB90@microsoft.com...
> Could it be unknown member hidden issue?
>
> "Jesse O." wrote:
>
>> I've had a weird issue when drilling down into a dimension. For the life
>> of
>> me I can't figure out what's going on.
>>
>> The cube has two dimensions - Date and Region. Region has two levels.
>>
>> For example:
>>
>> When looking at the top level total, Region 1 comes back as having
>> 15,000.
>> However when drilling down into Region 1, the number only returns 10,000
>> as
>> a total.
>>
>> Where are those other 5,000? It is incorrect across the entire dimension.
>>
>>
>>
>>