FlexReport: Subreport creates wrong page Numbers

FlexReport: Subreport creates wrong page Numbers

Posted by: j.reiser on 19 February 2026, 11:27 am EST

• 

  j.reiser

  • Post Options:
  • Link
    Copy

  Posted 19 February 2026, 11:27 am EST - Updated 19 February 2026, 11:33 am EST

  We’re almost done with migrating our report from another tool to FlexReport and have come across another small issue which I can’t resolve. I made a screenshot of the setup for better understanding of the architecture, see attachment (“architecture.JPG”). We created the report that way because we need a page header on the “Betriebsanweisung” part but not on the appendix.

  We have one report (called “Main”) with nothing in it, except that it hosts two sub reports in the detail section: The “Betriebsanweisung” report itself and an appendix containing images (“BilderAnhangEinträge”). We need page numbers on the first hosted sub report, but not in the appendix.

  If I preview the “Betriebsanweisung” report directly, page numbers are genereated correctly (“betriebsanweisung.JPG”).

  If I preview the “Main” report, page numbers are generated in the “Betriebsanweisung” report as well, but they are wrong an show “2/2” on each page (“main.JPG”).

  Any help would be appreciated.

  

  

  1648×491 156 KB

  

  1634×452 155 KB

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 20 February 2026, 6:02 am EST

  Hello,

  Thank you for providing the details regarding your report migration.
  
  We have attempted to replicate the page numbering behavior you described, but we were unable to reproduce it on our end. To help us investigate this further, could you please provide a stripped-down version of your report along with some dummy data?
  
  Having the actual report layout and the “Main” report setup will allow us to closely examine the cause and we can try finding a solution for you. Please let us know if you have any other questions.

  Regards,
  
  Uttkarsh.

• 

  j.reiser

  • Post Options:
  • Link
    Copy

  Posted 20 February 2026, 6:32 am EST

  Hi Uttkarsh,

  thank you for investigating our issue. I prepared a ZIP file containing the MSSQL 2025 database and our report file. This should allow you to reproduce the issue.

  Strange, but promising, that this doesn’t happen in your tests. Looks like there might be a solution for the problem

  Regards,

  Johannes

  Backup.zip

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 23 February 2026, 8:11 am EST

  Hello,

  Thank you for your patience and for providing the ZIP file with the database backup and report.
  
  However, we are currently experiencing some difficulties restoring the MSSQL 2025 .bak file in our environment. To ensure we can investigate this as quickly as possible, could you please provide the dummy data in a more portable format? An Excel file, JSON file, or an MDB (Access) database would be ideal and would allow us to replicate your environment immediately.
  
  Additionally, since our forum is a public portal, we want to ensure your data remains secure. If you would prefer to keep this investigation private, you can raise a support ticket through our My Support : https://developer.mescius.com/my-account/my-support
  
  This creates a private channel between you and our engineering team where you can safely share your files. Please let us know how you would like to proceed!

  Regards,
  
  Uttkarsh.

• 

  j.reiser

  • Post Options:
  • Link
    Copy

  Posted 23 February 2026, 9:41 am EST

  Hi Uttkarsh,

  I created an accdb (MS Access) file and opened a new case as proposed. I tried JSON first but got faulty results when exporting that from SQL Server (like unwanted line breaks, encoding issues,…) If you need further information, just let me know.

  Regards,

  Johannes

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 24 February 2026, 5:53 am EST

  Hello,

  Thank you for sharing the details on the support thread (ID: CAS-61010-N9Q2H1).
  
  We will review the information and get back to you there with updates shortly.

  Regards,
  
  Uttkarsh