NextCombinationPrintStep not fired during export

English Forum
,
1

Hi Oliver

With Export method, the “NextCombinationPrintStep” will not be triggered. Is there any way that we can change the variables when moving to the export of next project file?

Regards
Philip

2

Hi,

Where or how were the project files for the combination print designated for export defined? I attempted to test this in the provided export example, using the following code:

...
string file1 = "simple.lst";
string file2 = "simple.lst";
string projectFile = file1 + ";" + file2;
ExportConfiguration exportConfiguration = new ExportConfiguration(LlExportTarget.Pdf, fileNameTb.Text, projectFile);
exportConfiguration.ShowResult = _showFileCheck.Checked;
...
LL.NextCombinationPrintStep += LL_NextCombinationPrintStep;
...
private void LL_NextCombinationPrintStep(object sender, NextCombinationPrintStepEventArgs e)
{
    System.Diagnostics.Debug.WriteLine(e.ProjectFileName);
    (sender as ListLabel).DataSource = ;
    (sender as ListLabel).Variables.Add(...);
}
...

At my end, the event LL_NextCombinationPrintStep is triggered twice, and at this point, you should also be able to switch the data source/variable, etc. And I will get the in the created PDF file both projects (in my test case the same!) exported.

3

Hello Oliver
Thanks for your quick response.
I found that the reason for my Export not triggering the NextCombinationPrintStep was because, I had three layouts, of which one was “TOC” and another one was “IDX”. I found in the documentation that the “TOC” and “IDX” are not considered as separate layouts. So in effect there was only one layout. When I added one more layout, then the event was triggered.
Is there any event that would be raised in the case of “TOC” and “IDX” also?

Thank you once again for your response!
Regards
Philip

4

Hi @Oliver_Hambrecht,
hi @Philip_Mathew,

Thank you for your active participation in our forum and this thread.

Currently, in the combination print, it is not possible to explicitly address TOC or IDX, as these have always been handled internally. However, for the upcoming product version, we are planning several enhancements in the area of combination printing. This will include triggering the NextCombinationPrintStep event for these report sections. This specific request has already been documented here in Idea Place Improvements to Combination Print - feel free to vote. :wink:

Regards,
Daniel

2 Likes