Rank 1
Iron
I have a use case of trying to make a report that displays tax statements for one or more accounts. It essentially repeats the whole report for each account, appended together. I fetch the account data from SQL using a JSON string report parameter. The report has the following requirements:
Page headers and footers that display some basic report info labels passed in from the JSON string on each page of the report.
Directly above and below the previously mentioned footers, an extension of these sections that displays more detailed information fetched from sql. The extended header is pretty basic and can be the same on every page of the report. The extended footer displays some info that is account-specific and additionally, dynamically shows a payment stub label and table if this is the last page for a specific account's statement (i.e., the detail section's grouped table finished printing on this page).
The detail section displays a grouped table for the account statement that may run across pages but must not push around the header or footer.
Additionally, after the last page of the account statement, there may be one or more additional pages printed with another grouped table about that account. The layout at this point no longer really matters and any of the aforementioned sections and requirements could be left out. We particularly would not want the payment stub footer displayed here if possible, or at a minimum have it be blanked out.
Note again that after the account statement and the optional additional pages are printed for an account, this whole procedure may run again for another account in this report which is then appended in this same pdf.
I have attached a basic wireframe to show our use case, since I'm aware this is a lot. I have a suspicion that this is something that could be accomplished using group headers and footers but could use some pointers on how exactly to configure them to do what we want here. I mostly have experience writing reports that rely on grouping data sourced tables within the detail section, but this doesn't seem good enough for this report since we need data within the footer which has to have static vertical layout on each page and also match up with which account the detail is displaying.
I can think of solutions or workarounds for most of these problems, but the footer is especially concerning. Any help that could be provided to solve at least that issue would be greatly appreciated!
1 Answer, 1 is accepted
Rank 1
Iron
I can't find out how to delete this question, but I was able to find answers for most of this, so posting them for posterity.
https://www.telerik.com/forums/cannot-get-grouping-to-work
The idea is to move the data to the report level, move all data items into group headers/footers for the report, and use bindings to set ReportItem.DataSource = ReportItem.Parent.DataObject. The group header can be expanded to also act as the detail, and the footer can be set to always print at the bottom. This addresses 90% of my use case.
The only missing piece is how to print the information that should only go on/after the last page of a group (account). Two-tiered grouping could probably solve some of this, but it's not perfect. Some sort of conditional display that can figure out if the group has finished on the current page would be ideal. There may be some sort of Last field I can check, else a hackier solution might be to bake a field into the data to signify this.