Unfortunately, I don’t believe it’s possible to alter the height of master pages (and even the content areas that they contain) at runtime. The implications to the layout engine would be large.

You can, however, change what page a subform is placed on at runtime. That means you would have to have some preset master pages and you would choose the one that is the best fit.

To change the page on which a body page subform is placed, you can do this:

// JavaScript:
BodyPage.resolveNode("#breakBefore").target = "Page2";
xfa.layout.relayout();

The script above assumes that you have configured the BodyPage subform to be initially placed on a specific page (e.g. a default page) otherwise it won’t work because the < element won’t exist for the BodyPage subform. You can place a subform on a page by setting the “Object palette > Pagination tab > Place property” to “On Page {X}”.

It’s good that you have your header and footer on the master page. All you need to do is make sure that the content area (rectangle with a pink-ish border on the master page as well) does not overlap your header and footer. The content area (there can be more than one) determines where content from the body pages can flow into pages generated at runtime. Therefore, to ensure you table doesn’t overlap your header and footer, make sure the content area restricts it to the space in-between them.

I’m fairly new to LiveCycle too, and was wondering if there’s any way to set the Master Page height dynamically based on the height of the subform that contains my input fields?

My forms aren’t intended to be printed, so what I’m trying to do is eliminate any pagination that is caused as the various fields are made visible/hidden.

I started to solve the problem by manually setting the Paper Type (in the master page tab) to ‘custom’, then choosing a height that would acommodate all the fields if they were visible, but this meant there was often a lot of white space at the bottom of the form. So next I tried to set the master page height to the same as the subform that contains the fields – and that’s where I’ve got stuck. I’ve tried manually setting the paper type to custom, then changing the master page height using:

form1.#subform[0].Button1::click – (JavaScript, client)
var newHeight = xfa.layout.h(xfa.resolveNode(“form1.#subform”), “in”);
xfa.form.form1.Page1.h = newHeight + “in”;

…but I’m having no luck and I’d be grateful for any help!

Thanks in advance

Ben

You call the field on the master page a “floating field”. To me, that means a field that you inserted into a text object by clicking in a text object and choosing the “Insert > Floating Field”. Is that really what you mean?

The page number is a floating field as well, but it gets its value programmatically, not from data.

Your other field likely has a data binding. What kind of data are you wanting to merge into this field and what is the desired result? Is it one value per page?

Like most people I have a problem.

I am using LiveCycle 8.2 ES to develop a dynamic flowing form. This form, when opened in Acrobat 8 or 9 will import data from an xml file and populate floating fields accordingly.

I have 1 master page with a current page number, and a floating field. Both have to be placed in a specific place on the form to meet state regulations and this is why they are on the master page.

My issue is when I import the data the floating field on the master page will populate on the first page but not on any others while the current page continues to populate accordingly.

I would like to keep the floating field on the master page if at all possible since I have tried to use the footer option available but to no success. It keeps placing the footer at the very end of the content not in the specific are of the form where it needs to be.

I appreciate any assistance you can provide.

thank you for your time

You can for a master page to be used only on the last page of a form by using XFA’s Simplex/Duplex feature which you can activate by selecting a pageSet (named “(Master Pages)” in the Hierarchy palette) then setting the “Object palette > Page Set tab > Printing property” to something other than “Page Occurrence”. Then select a master page and set its “Object palette > Pagination tab > Master Page Applies To > Placement property” to “Last Page (in Page Set)”. Then you can set the table’s pagination to place it on that special master page, thereby ensuring that the table ends-up on the last page.

But even simpler is just to make your body pages flow and put your table inside a subform that is as tall as a page, doesn’t allow page breaks in its content and is located after all other content in the form. This will also ensure that the table ends-up on the last page (and on a page of its own).

As long as the PDF form has been extended to allow attachments, you should be able to add attachments using Reader. Acrobat always allows adding attachments.

Designer cannot be used to add attachments to the PDF and editing a form (in Designer) that has attachments may cause those attachments to be lost.

Unfortunately, there’s no easy way to do this. Text doesn’t “flow” from one text field to another without some cleaver coding (not exactly what you want, but the principle is the same).

I have another question… Requests for new functions and designs come in every day.. This one is to add a required Revision table only at the end of the form. I was thinking of adding it to the Master Page somehow, but I would need to use a second master page to make the table be only on the last page.

BACKGROUND:
I have one Master page at this time; it has repeating information on each form page. This is how it needs to be.

How can I add a “last Master page” – or – a required table for revisions that needs to appear at the very end of a form.

Because only those in control of the doc revision will have access to the fields, I think the table needs to be on a Master Page. I could be wrong.

I guess my real question is: How and where do I place a Master Page that appears at the end of the document only, not on each page. Or if I don’t need it on a Master Page, do I protect it somehow but allow the Doc team access so they can revise it when needed?