Top level element showing 0 when N levels that roll into it have values

[wigglyrat]

Hello: I have an issue with a consolidated element that appears as 0 when there should be a value present.

This is after making a change to a TI that was modified slightly with a new variable added. Prior to adding the variable,
the alignment had gone off with their order in the data source and the order in the variables tab in in the TI, which led to
no values appearing in the variable that was out of alignment.

Before correcting this the 'All Values' consolidated level worked fine. After correcting the alignment, i.e. reloading the data source
to reload variables in the variables tab, the 'All Values' consolidated level now shows as 0, even though there are clearly values in
the lower levels. I've checked weightings which look fine. The dimension structure hasn't changed. Does anyone know what the issue
might be here?

Many thanks in advance,

[tomok]

Hello: I have an issue with a consolidated element that appears as 0 when there should be a value present.

This is after making a change to a TI that was modified slightly with a new variable added. Prior to adding the variable,
the alignment had gone off with their order in the data source and the order in the variables tab in in the TI, which led to
no values appearing in the variable that was out of alignment.

Before correcting this the 'All Values' consolidated level worked fine. After correcting the alignment, i.e. reloading the data source
to reload variables in the variables tab, the 'All Values' consolidated level now shows as 0, even though there are clearly values in
the lower levels. I've checked weightings which look fine. The dimension structure hasn't changed. Does anyone know what the issue
might be here?

Many thanks in advance,

Sounds like unfed, rule-calculated cells.

[wigglyrat]

No that can't be it as it's a new cube / does not have any rules yet. Thank you.

[Steve Rowe]

This can only really be a structure problem with the dimension or an issue with the data, the following options spring to mind.

The data isn't being loaded to the place you think it is and so consolidation returns zero.
The data is being loaded to the correct location but nets to zero.
The children of the consolidation have zero weighting or the weighting means the data nets to zero.
The consolidation doesn't contain the children you are loading the data against.

In a no rule cube there is no complexity so there is really nothing technical to go wrong, there must be an issue with the data loader or the dimension.

What do you actually see in the cube viewer when you drill down on the C level?
Have you tried right clicking on the cube and ascii outputting so you can double check where the data is being loaded?

Cheers