Quantcast
Channel: SQL Server Reporting Services, Power View forum
Viewing all articles
Browse latest Browse all 10045

hiding columns in reporting services

$
0
0

Hello

We use reporting Services to report data from CRM.

I have a tablix that has about 100 columns grouped in about 4 groups. I would like to offer the option to collapse some colums
My idea would be that you start with all groups closed; and you click on a groupname to see all the fields under it.
This table is a simplified view on how my tablix looks now. With the grouping values being inputted manually; as I have no better way of doing it.

groupAgroupBgroupC
| A:field1| A:field2| A:field3| B:field1| B:field2| B:field3| C:field1| C:field2| C:field3
| content| content| content| content| content| content| content| content| content
| content| content| content| content| content| content| content| content| content
| content| content| content| content| content| content| content| content| content
| content| content| content| content| content| content| content| content| content

In the above table it looks like the grouping cells merge across 3 columns. this is not the case: groupA|emtpycell|emptycell|groupB|emptycell|...
I can make it so that for example only C:field1 is visible. When I click groupC C:field2 and C:field3 become visible.

The problem I still encounter is that when I click groupB, I hide all fields on the right of B:field1; also all the groupC fields.


I achieved the above situation by selecting all the columns that should be hidden; set the visibility to hidden and set the toggleitem to the name of the textbox of the group.

What I wish to achieve is that in collapsed state; I would have alltogether 3 visible columns, the ones containing the groupname and field1. I can choose to open one group individually.

I hope this does make some sense?

Can someone advice me on how to reach this?







Viewing all articles
Browse latest Browse all 10045

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>