Post reply

Add a Sub Report (if that is what I really want?)

  • April 5, 2012 at 1:57 pm

    #259494

    I am very new to SSRS...I am attempting to create a SSRS report that will display some general invoicing information (Invoice#, Posted Date, Bill To Org, End Customer, and Invoice Amount). I have this part done, shown in a table, able to pass in a Invoice Number as the parameter, can view the information in BIDS etc...

    What I need to do is show the specifics of the particular Invoice on the report in what I believe would be a sub report (this may not even be the best way to do it). The information I want to convey here is the Part Name, Part Number, PO#, and the Amount of each Part. I do have common fields (Invoice#) between the two datasets, so I should be able to "join" them.

    I have my queries for each dataset, I just can not figure the best way to implement this in my SSRS report. Is a sub report the way to go? Is there a better way to do this.

    I have Googled so much and nothing seems to help (or make sense)...Any and All help will be greatly appreciated!!

    Thanks

  • April 5, 2012 at 2:23 pm

    #1469827

    If I understand your requirments, you have an invoice header and detail and you want to display both on a report.

    I would query the header and detail data in a single query. There are 2 ways you might approach the report itself.

    First would be a grouped report. Add your detail columns to the report. Then right click on the row with the detail and select Add Group >> Parent group and include a header. Then add the header data in the new grouping row that is built above the detail. If you have lots of header data, this format may be a bit unweildy.

    Another approach would be to add a list box to the report that is grouped on the Invoice level. Add text boxes and labels to the list box for all your invoice header data. Then add a tablix to the list box and add your detail data to the tablix. This will probably give you a more classic looking invoice style report, but it is a bit more difficult because the grouping is not always obvious on how to configure.

    In both cases you really only need a single dataset with both detail and header information.

  • April 6, 2012 at 5:02 am

    #1470027

    Hey Daniel, Thanks alot for the reply. I am going to attempt to implement your first suggestion as I do not have that many header columns.

    Let's hope it goes OK for me...

    Thanks Again.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply