From: dbuchanan on
Is there a work around to remove the aggregate information from the matrix
data region.

Context:
I am using the Data Value " =First(Fields!data.Value) ". This is what the
wizard appropriately chose because of the natrue of the underlying data I am
supplying.

The data I am supplying is text data - the customer wanted inconsistent
datatypes displayed in the same field - dates or percent data displayed as
text based on a mutually excusive condition.

To accommodate the customer's request I created a case statement using
conditionals and calculated fields to convert both data to formatted text.
It is that formatted text column which is displayed for data.

The result the is that the field displays as the customer requested but the
trade-off is that the matrix report - which is designed to aggregate data -
now does not know what do with it except to display the first value.

So now the customer does not like what shows for aggregated (rolled up
values) removed.

I was well on the way to providing a solution with a different report
configuration but the end customer was gettng impatient to see something so
my customer urged me to do anything I could to deliver a report - so we are
back to trying to find a way to remove the "aggregated" data for all levels
but the actual data at the bottom of the hierarchy.

I understand it is the nature of the report to do just what it does, however
is there a work around to remove the "aggregated" data and leave the bottom
level data?

What can be done to do this?

Thank you,
Doug


From: "Charles Wang [MSFT]" on
Hi Doug,
I could not understand your meaning clearly. For a matrix, given one X-axis
value and one Y-axis value, the data will be only one aggregated value. If
you want to show multiple values in the data area, that means, you have to
duplicate the X-axis value or the Y-axis value multiple times, however this
is not appropriate for a matrix data region. In this cause, you need to
consider using a Table data region. If you also want some matrix function,
in SQL Server 2005, you can use PIVOT statement to create a T-SQL statement
that can provide similar function like a matrix, so I think that you can
write a (may be a complicated) T-SQL statement to produce the expected
result in tabular form. After that you can directly drag the data into a
Table data region.

You may refer to:
Using PIVOT and UNPIVOT
http://technet.microsoft.com/en-us/library/ms177410.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg(a)microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

 | 
Pages: 1
Prev: User Access
Next: Strange pagination problem...