Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
muzzettemm
Posting Yak Master
212 Posts |
Posted - 2009-07-05 : 21:47:40
|
Hi I have two groups one is the state category the other is the state services. and I am trying to hide the duplicates for the state categorylooks like this. Selft ConceptCultureSelf Concept Youth leadershipAcademic SupportLarge GroupI only need the State Categories to show up one time not every time there is a State services that relates to it, (hope that makes sense) when I went to the properties to hide the duplicates it didnt work. Is there another way to do that?? |
|
SQLSoaker
Posting Yak Master
169 Posts |
Posted - 2009-07-06 : 11:28:12
|
You should just have to group this in the tabular design. Make it a grouping and not a detail.Should have a 1 with a line on top and on side of it to only display it once. |
|
|
muzzettemm
Posting Yak Master
212 Posts |
Posted - 2009-07-07 : 00:39:26
|
I did group it in the tabular design. And I made it a grouping not a detail |
|
|
SQLSoaker
Posting Yak Master
169 Posts |
Posted - 2009-07-07 : 12:37:13
|
quote: Originally posted by muzzettemm I did group it in the tabular design. And I made it a grouping not a detail
Then it should only show once based on the grouping. Go to the properties and make sure that the "Group on" expression is the field you want to group on. |
|
|
muzzettemm
Posting Yak Master
212 Posts |
Posted - 2009-07-07 : 16:09:59
|
ok I will, thank yoiu |
|
|
muzzettemm
Posting Yak Master
212 Posts |
Posted - 2009-07-08 : 00:37:06
|
ok all taken care of now thank you |
|
|
RobSchripsema
Starting Member
1 Post |
Posted - 2009-12-08 : 15:51:10
|
I've had to do something similar, but didn't want to create another "level" of grouping, since 99% of the detail records were completely unique, and only a few had duplicate fields, in which case I simply didn't want the duplicated part to show up. (Specifically, they were purchase records, where the query returned a full row of data for each line item in a purchase, most of which were of a single item, some of which were of two items listed for the same purchase -- but with duplicated date/customer/tag#, etc.)What I did was use an expression to create a toggle on the visibility of individual text boxes in the row using the "previous" function. The records were sorted on a sales ticket number, and a second record on the same ticket would have the same ticket number as the previous row in the dataset. So, if I didn't want the customer text box to show up for that line (as a visual indicator that it was being associated with the previous line/ticket), I set the visibility to "=(Previous(Fields!TicketNum.Value) = Fields(!TicketNum.Value))". Note that the visibility expression is actually the value for a "Hidden" attribute; i.e., if true, the field will be hidden; if false, it will be visible. I repeated this for each field on the row that should not be displayed, and left the other fields (Qty, SKU, price, etc.) visible always.A bit tedious, but very slick, doesn't require the extra level of grouping and allows for selective display of column data for a row.Rob SchripsemaIntegra Software & Services |
|
|
|
|
|
|
|