Table rows are rendered on the next page after DOCX to PDF conversion using Java

I have 3x3 table.
All table rows, except for the last row, have paragraphs with pagination option Keep with the next.
In the middle row, a paragraph has property Page break before.

If document is exported to Word -> whole table is kept as a single unit.
If document is exported to PDF -> table is split.

How to fix PDF export and keep table together?

Using: Aspose.Word JAVA 20.7

Adding exported DOCX/PDF files below and code snippet for case recreation.

issue_code_and_examples.zip (54.1 KB)

@drizgelis

Please use the latest version of Aspose.Words for Java 20.9 and apply license before importing document into Aspose.Words’ DOM to get the desired output.

You can get the temporary license from here:
Get a Temporary License

@tahir.manzoor
Thanks for the suggestion but that does not work. Did it work for you with 20.9 Aspose.Words version?
Everything okay is with the license, just running public static void main does not catch it.

@drizgelis

We have not found any issue with output document. The documents you shared in the first post contains the evaluation watermark. Please make sure that you have set the license correctly.

@tahir.manzoor

I would like to ask you to run the attached code and produce the output in DOCX and PDF formats (code template is prepared, just comment / uncomment).

If it is the same, please attach the files as a proof.

For the sake of proving, that evaluation watermarks does not have ANY relation to the produced problem, please check attached compiled documents without the watermarks.

Documents were generated with the latest - 20.9 - Aspose.Word JAVA library.

aspose_20_9_no_evaluation_mark.zip (8.3 KB)

@PROCUREMENT2

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 WORDSNET-21146 . You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

The issues you have found earlier have been fixed in this Aspose.Words for .NET 20.12 update and this Aspose.Words for Java 20.12 update.