We discovered some very odd matrix behavior a couple days ago and just today found out what in the RDL seems to be causing the issue. The issue is that certain cells in the matrix will not be populated if a certain report parameter is defaulted.
The basics: A matrix report with 6 report parms two of which are passed to the underlying procedure call. There are 6 datasets behind the report. 4 are related to getting date and timespan information to allow for parameter defaulting.
1 gets a list of customers to populate a selection drop down and the last gets the data.
The data query takes a customer name and an end date. Via the report parameters the end date parm is defaulted based on a dataset which is chained through the other parms and associated datasets.
The matrix is used to show a months worth of activity by day. There are two int32 data points in each matrix cell one is a total and one is a failure count. The data as returned by the reporting proc is already summarized so no aggregate is needed
in the matrix. However, using SUM or not in the matrix cell makes no difference to the strange outcome.
When the report is run with the end date parameter being defaulted one of the rows will incorrectly show 16 cells. The cells appear as if there is no data. However, if the proc
View Complete Post