Column grouping weird behavior

• mario17

  SSCertifiable

  Points: 6079

  More actions

  April 1, 2014 at 10:30 pm

  #285296

  Hi,

  I have report with row and column groupings for dataset like below, have

  CustID, AMT as row group

  YYYY, QUARTER as column group

  so 777 cust ID does't have entry for 2014/4q and I expect his box be empty but instead it got populated with value for CustID = 1000 for 2014/4 (4000). Don't know what could be wrong. This is old rdl, I took dataset to freshly made rdl and it works as designed, but I still want to make old rdl work, is there any secret property that can be changed.

  I checked/played with old rdl and match all goupings and still a problem.

  Tx

  M

  SELECT 1000 CustID, 1 QUARTER, 2014 YYYY, 1000 AMT UNION

  SELECT 1000 CustID, 4 QUARTER, 2013 YYYY, 1000 AMT UNION

  SELECT 1000 CustID, 2 QUARTER, 2014 YYYY, 2000 AMT UNION

  SELECT 1000 CustID, 3 QUARTER, 2014 YYYY, 3000 AMT UNION

  SELECT 1000 CustID, 4 QUARTER, 2014 YYYY, 4000 AMT UNION

  SELECT 777 CustID, 1 QUARTER, 2014 YYYY, 710 AMT UNION

  SELECT 777 CustID, 2 QUARTER, 2014 YYYY, 720 AMT UNION

  SELECT 777 CustID, 4 QUARTER, 2013 YYYY, 720 AMT UNION

  SELECT 777 CustID, 3 QUARTER, 2014 YYYY, 730 AMT

• pietlinden

  SSC Guru

  Points: 63503

  More actions

  April 1, 2014 at 10:59 pm

  #1702319

  Sorry, can't fix what I can't see, but if you drop a matrix into your report with

  ROW Groups: [CustID]

  COLUMN Groups: [Year], [Quarter]

  Intersection: SUM([Amount])

  I think it will do what you want. (I attached a slightly modified example - I just renamed a few columns because they're reserved words in T-SQL.)