Excel shows #N/A for valid OLAP cube values

[Glenn Coello]

We are having problems in our organization with valid cell
values from an OLAP cube showing up as #N/A when the cube
is imported into a Pivot Table in Excel.

The measure is a simple sum aggregation. The correct
value shows up in Analysis Services, when creating an MDX
query, and when viewed on the web using the Business
Objects OLAP viewer. The #N/A doesn't appear on all cells
only some cells.

Interestingly enough, even though the values in the cells
is displayed as #N/A, the totals for all of the parent
levels are correct.

Can anyone provide me with some input?

[Olivier Matrat]

Hi

Maybe you have special formatting options for your PivotTable (like #N/A for
empty cells in Table Options for instance ?)

Otherwise, could it be that you are not executing the exact same query in
Excel (I am thinking of the slicer part of the query in particular) ?

Another thing, are there any calculated members for the incriminated cells
that could cause the errors? In that case the calculation could be right at
the top of a hierarchy and wrong at the bottom since calculations are
typically made in MDX at all levels independent from the others.

Was your cube write-ebabled? If so, failure to connect to the relational
write-back table couldalso result in errors...

Also, I have seen problems occur when Excel add-ins from several vendors are
installed at once on the same client.

What version of Excel PivotTables are you using?

Those are just a few pointers...

HTH

Olivier.

Post by Glenn Coello
We are having problems in our organization with valid cell
values from an OLAP cube showing up as #N/A when the cube
is imported into a Pivot Table in Excel.
The measure is a simple sum aggregation. The correct
value shows up in Analysis Services, when creating an MDX
query, and when viewed on the web using the Business
Objects OLAP viewer. The #N/A doesn't appear on all cells
only some cells.
Interestingly enough, even though the values in the cells
is displayed as #N/A, the totals for all of the parent
levels are correct.
Can anyone provide me with some input?

[kathy]

Olivier Matrat wrote on 08/12/2004 09:07 ET

Post by Olivier Matrat
H
Maybe you have special formatting options for your PivotTable (like #N/A fo
empty cells in Table Options for instance ?
Otherwise, could it be that you are not executing the exact same query i
Excel (I am thinking of the slicer part of the query in particular)
Another thing, are there any calculated members for the incriminated cell
that could cause the errors? In that case the calculation could be right a
the top of a hierarchy and wrong at the bottom since calculations ar
typically made in MDX at all levels independent from the others
Was your cube write-ebabled? If so, failure to connect to the relationa
write-back table couldalso result in errors..
Also, I have seen problems occur when Excel add-ins from several vendors ar
installed at once on the same client
What version of Excel PivotTables are you using
Those are just a few pointers..
HT
Olivier
"Glenn Coello" wrote i
messag
news:060801c47ff7$db3575a0

Post by Glenn Coello
We are having problems in our organization with valid cel
values from an OLAP cube showing up as #N/A when the cub
is imported into a Pivot Table in Excel
The measure is a simple sum aggregation. The correc
value shows up in Analysis Services, when creating an MD
query, and when viewed on the web using the Busines
Objects OLAP viewer. The #N/A doesn't appear on all cell
only some cells
Interestingly enough, even though the values in the cell
is displayed as #N/A, the totals for all of the paren
levels are correct
Can anyone provide me with some input

Check the permissions for the Role. Under "Cell Data", unchec
"Enable read permissions".