My second table pointed to its own dataset seems to be grouping itself on the 1st data set
Dataset 1 returns a users and their AD info. Dataset 2 is a list of users, their role and a coulm for the count of matching roles that are in the same ad groups. DS1 binds to Table1 DS2 to Table2. The only connection between the datasets is they use the same parameter @UserId to pass to their separate stored procs. So for testing I just have the tables side by side. When I run the report for user PPX1 table 1 comes out fine, table 2 was initially returning 52 records, one for each matching AD role. But when I either hide duplicaes or use the hidden properties of the row to hide dupes I get one record and then the next record like 2 pages further in. Why is it when I hide duplicates the next available record does not show? Thanks, Phil
September 28th, 2012 5:06pm

Hi, if you want to hide the entire row based on a duplicate field value, following thread might help you. http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/136fdd3a-af71-4e8f-ac8d-2f6ef02066c9 Aftab Ansari
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2012 5:32pm

Thanks for the tip. i found out I needed to move my data from the detail to a group header and then hide the empty detail row.
September 28th, 2012 5:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics