the table has to look likes Level1 Level 1.1 Level 1.2 Level 1.3 Total Level 1.1+Level 1.2+Level 1.3 Level2 Level3 Level4 Total Level 1.1+Level 1.2+Level 1.3 + Level 2+Level 3 + Level 4 I can't achieve this desing/ groups/ totals, I can play with data, add extra columns if it needs any ideas how ?

I think all this is possible but I would need to understand your data and business case in order to help. In your example, you showed levels 1, 1.1, 1.2 1.3, 2, 3, etc. Is level 1.1 really a group after the group for level 1. If so, what is the difference between group level 1.1 & group level 2? Perhaps it would make more sense if you were to provide the column names and explain the hierarchal relationship between these fields. A table can contain one hierarchy of nested groups. Another hirarchy of groups would normally be contained in a different table. Please provide some details so we can understand your scenario.Paul Turley, MVP [Hitachi Consulting] SQLServerBIBlog.com *Please vote if helpful*

the logic of data looks like ReportLevel1 ReportLevel2 $ Level1 Level1 $ Level1 Level 1.1 $ Level1 Level 1.2 $ Level1 Level 1.3 $ Level2 Level2 $ Level3 Level3 $ Level4 Level4 $ I can change the logic of data, it's extracted rows from DWH, my problem is that I can't achieve this "grouping design" with inetrmediate sub-totals Level 1.1+Level 1.2+Level 1.3

the logic of data looks like ReportLevel1 ReportLevel2 $ Level1 Level1 $ Level1 Level 1.1 $ Level1 Level 1.2 $ Level1 Level 1.3 $ Level2 Level2 $ Level3 Level3 $ Level4 Level4 $ I can change the logic of data, it's extracted rows from DWH, my problem is that I can't achieve this "grouping design" with inetrmediate sub-totals Level 1.1+Level 1.2+Level 1.3