Page Break within a table in quote form does not format the header row correctly on the following ro

[thomas_hermann]

Hi,

I am designing the quote document via Adobe LifeCycle Designer and have a problem that can also be reproduced with the standard form template “Sales Quote Demo”.

Some articles have a long additional text (txtContent in frmCustomerInformation), which should be printed, but on the first page - where the table starts just over halfway due to the header information with address etc. - there is not enough space. By default, the whole line is printed on the second page, where it has enough space.
Now, however, the text should be paginated instead so as not to waste space unnecessarily.
I have therefore activated the property “Allow Page Breaks within Content” both in the subform “frmCustomerInformation” and in the parent “rowRemarkRow”.

As a result, it breaks the content as desired, but the header line is now displayed very unattractively and completely unformatted halfway into the text.
I would actually like it to always start with the header on the following page and then repeat it per line.
In general, it does it correctly, but I can't get the header line to look nice.

Can anyone help me here?

Kinds Regards,
Thomas

[Ryan-Crosby]

Given the screenshot I would assume your header row is setup using western text flow, but to avoid this problem you would want to render it using a positioned subform.

[thomas_hermann]

Hi Ryan-Crosby,

thanks for your answer, that sounds quite logical.

For the hdrTableHeader element, however, I only have the choice between Type: Header Row, Body Row and Footer Row as well as Layout: Left to Right Row and Right to left Row.

If I set the parent subform frmTableBlock to Posititoned instead of Flowed, the option “Include Header Row in Subsequqnet Pages” is deactivated for the header element. Without this, it never repeats the header row anyway.

Here again the current pagination setting, with which it pushes the header row together on the following page, as can be seen in the first screenshot.

Do you have any additional ideas?

Kind Regards,
Thomas

[Ryan-Crosby]

I can't provide guidance on using tables because I find them klunky and never use them, but I bind tables directly to subforms with the a top subform tied directly to the table instance and two child subforms - a positioned one for the header row, and a flowed one for the item data. This approach works quite well for any page break scenarios and is pretty easy to create in LC.

[thomas_hermann]

Is there an easy way I can convert this from an existing table or do I have to completely redesign it?
I am only offered “wrap in subform” for the whole table, not for individual elements like header or row

I had made it easy for myself and adapted the existing standard layout (which is based on a table) to our needs. In the meantime, however, there is already a lot of customization with scripts etc. in the table rows.
The buggy page break was actually the last customization I wanted to implement.

[Ryan-Crosby]

No options that I'm aware of but for six fields (guessing from screenshot) it shouldn't take too long to manufacture it from scratch - I could probably do it in less than 10 minutes. The only difficulty would be migrating over whatever script logic you have and testing it out. I'm accustomed to setting it up this way and creating a single header and item field to start for setting basic formatting and then copy/pasting the remaining elements and shifting focus to widths & bindings.