Reportcombiner - parameter and page options

Reportcombiner - parameter and page options

Posted by: mdynna on 8 September 2026, 12:55 pm EST

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 8 September 2026, 12:55 pm EST

  We’re looking at using the Reportcombiner class to allow the user to combine multiple customized PageReports for printing. We’re noticing two things:

  1. Even if the two reports have identical Parameters, the Parameters are duplicated when combined. The combiner adds a “_2” to the name of the Parameters. Is there any way to modify this behaviour? We’d like the user to only need to enter the parameters once and have them be used for all reports.
  2. The PageBreakBefore property on the LocationOptions class seems to have no effect. Second and subsequent reports always start a new page. Is there some other property on the Page report that would force the report to go to a new page even when PageBreakBefore is False?
• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 9 September 2026, 2:19 am EST

  Hi Mark,

  1. Yes, for two identical parameter names, the report tries to remove any conflicts between the value of the parameter in the first report and the second reports. Hence, it adds an ‘index’ to consecutive parameters.
     
     If you would like to reuse the first parameter value in the second report, then you’ll need to manually remove the parameter from the combined report and change the reference to that parameter in your second report to reference the parameter from the first report.

  2. Yes, by default the reports are combined as ReportSections, so the second report always starts on a new page. If you want to start it after the first report itself, then change the ‘combiner.Mode’ to ‘CombinerMode.SubReport’. This will add the subsequent reports as a SubReport and hence will start consecutively where the first report ends.
     
     However, do note that the SubReport removes any header/footer of the page, so you may observe that the combined report is missing any header/footer. Therefore, this method is no longer recommended and is deprecated.

  Please find attached a minimal sample application implementing the above two approaches for your reference.

  Also, if you have no issues with the SubReport approach (i.e. the header/footer of pages getting removed) then we’ll recommend adding a SubReport to your main report and referencing the second report from there or creating a separate report with two subreports referencing both of your reports.
  
  This way, you can still use the common parameter without any workaround, and the subsequent report still starts after the first report without the risk of deprecated properties being removed in future versions.

  Regards,
  
  Anand

  ReportCombiner.zip