PageHeader in report an sub report


We use a template jasper report to set up common headers and a subreport for the actual report.

When we try to use <pageHeader> in the subreport the first report page outputs as a page header in .docx.

Hi there,

Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:

  • Please share the .jrprint file.
  • Please attach the output Word file that shows the undesired behavior.
  • Please attach the expected output Word file that shows the desired behavior.

As soon as you get these pieces of information ready, we’ll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click ‘Reply’ button that will bring you to the ‘reply page’ and there at the bottom you can include any attachments with that post by clicking the ‘Add/Update’ button.

Zip file with required files attached.

I worked with aspose-words-jasperreports-6.3.0.jar implementation version 17.3.

Hi there,

Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSJR-215. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hello, this is a mission critical bugfix request for Aspose Words for Jasper reports. This is for Merck, who bought the Aspose licensed product.
Can we get reliable timelines for the update of Aspose Words library with this issue fixed?

Hi there,

Thanks for your inquiry.

Currently, your issue is under analysis phase. Once our product team completes the analysis of your issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.


Do you have any update on WORDSJR-215 progress?

Hi there,

Thanks for your inquiry. Your issue is still under analysis phase. We will inform you via this forum thread once there is any update available on this issue.

We apologize for your inconvenience.