Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Invoice with different kind of detail lines

edited March 2014 in General
Hi,

For a project where the customer needs an invoice layout I am looking
for a simpler solution than my current implementation.

Case with this invoice layout is that the invoice lines represent
different information. A line can be a product, a project, a cost center
division etc, etc. Each line is printed with a different layout. Because
most lines are grouped together (project is often followed by multiple
cost center lines), a group should be started en ended with a group
header and footer.

Now I use a report with multiple subreports in the detail band. The main
report is connected to the invoiceline datapipeline, the subreports are
not connected to a datapipeline. At the start the subreports.top are set
to 0. DetailBeforeGenerate controls which subreport is visible based on
the invoice line type.

This works well without cluttering the detailband. The problem I have is
with the cluttering of the groupheader and footer. They contain elements
of different invoice line types.

For this situation it would be great to use title and summary of the
subreports but I can't get it to work.
The title should only be printed for the first record of that invoice
line kind. The summary should only be printed after the last record of
that line kind.


Using RB14.08
--
Kind regards,

Jeroen Röttink
JR-soft software solutions

Comments

  • edited March 2014
    Hi Jeroen,

    Yes, the subreports are independent containers. Their Title and Summary
    bands are going to print each time the subreport is printed (each detail
    band).

    One option would be to do something similar inside the Group Header and
    Group Footer bands as you are in the Detail band. Create a subreport
    for each type of invoice line and toggle their visibility based on the
    subreport that will be displayed in the Detail.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.