This is well-known behavior in Reporting Services - one work-around is
to create a Calculated Member:
http://msdn.microsoft.com/library/de.../en-us/dnsql2k
/html/olapasandrs.asp
Quote:
|
Integrating Analysis Services with Reporting Services
|
Sean Boon
Microsoft Corporation
June 2004
...
Another behavior of the flattening algorithm is that the "[(ALL)]" level
is not included in the dataset. This has a couple of implications. The
first is that if you want to include data from the "All" member of a
dimension, you'll need to create a calculated member to represent this
member. This can be accomplished in a couple of different ways. The
first method would be to create a calculated member on the Measures
dimension and for the definition of the calculated member refer to the
current member's name or unique name. There are several examples of this
method represented in later sections of this whitepaper.
Note The "All" level of a dimension is not included in the field set
that is returned to Reporting Services.
The second implication of the "All" level not being represented in the
dataset is that calculated members, usually defined without a parent
member, will need to change so that they do have a parent member. This
only applies in cases where the calculated member does not belong to the
Measures dimension. In many cases, when calculated members are defined
on a non-Measures dimension, the parent member property is left blank.
This can be changed in the calculated member dialog box as shown below
...
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***