Support project aggregation for master mode

Idea Place
1

I suggest to implement the following feature:

Based on the cool new LL26 feature Combine multiple projects in a single print job it would be awesome to have the ability to print every project for master mode record A, than every project for master moder record B …

A typical use case might be:

a) I have a customer that prints invoices with terms and conditions that do not fit on a single page. Thats why I can’t use the backside feature.

With

LL.DataSource = GetMyDataSource();
LL.AutoProjectFile = @"invoice.lst;toc.lst";
LL.Print();

this would be easy to achive.

b) The new feature has an important advantage over manually merging two preview files: The totalpages are shared between the combined reports.

This would not make any sense in master mode where I currently have

  • invoice 1 page 1
  • invoice 1 page 2
  • invoice 2 page 1
  • invoice 2 page 2
  • invoice 2 page 3

transferred to this new feature this would propably result in

  • invoice 1 page 1
  • invoice 1 page 2
  • invoice 2 page 1
  • invoice 2 page 2
  • invoice 2 page 3
  • toc 1 page 4
  • toc 1 page 5
  • toc 2 page 1
  • toc 2 page 2

which would look odd. Basically if this feature will support master mode I can only imagine use cases where I would like to have the reports merged based on the master records.

  • invoice 1 page 1
  • invoice 1 page 2
  • toc 1 page 3
  • toc 1 page 4
  • invoice 2 page 1
  • invoice 2 page 2
  • invoice 2 page 3
  • toc 2 page 4
  • toc 2 page 5
2

Our application works very similar. :+1:
We work with seperate print jobs and merge the results in our own preview.
This way we can show the preview asynchronous, while generating.

A possible solution to this would be to add duplicates of the “.lst” to achieve the same result.
This way you can print all kind of combinations.
And According to my information, it is possible to change the datasource (with seperate records) in every “NextCombinationPrintStep”-Event, depending on the next “.lst”-File.

LL.DataSource = GetMyDataSource();
LL.AutoProjectFile = @"invoice1.lst;toc1.lst;invoice2.lst;toc2.lst";
LL.Print();

But this way you get a “complete” Numbering through everything.

It would be great to have a Method ResetPageNumber() in the “NextCombinationPrintStep”-Event for more flexibility. I will open a sperate Topic for this:
ResetPageNumber() in the “NextCombinationPrintStep”-Event