When the "Row" allows page breaks, you also have to allow it for its parent object "Table" and its parent object (Page) …

You have to allow page breaks also for all surrounding subform(s) of the table.

You can't determine by scriptings if a fields value is too large for the fields visible area. There is simply no property in the field widget available that will inform you when this happens. The only information is the visible plus sign [+] in the fields corner.  The available methods (such as "lim...

Well, the total value per row should be calculated with:$ = Quantity * ValueAnd the page total with:$ = Sum(Row1[*].TotalValue)Both scripts are in FormCalc not JavaScript!

How does the structure of you table look like? Please upload you form or post at least some screenshots.

I think there is no form object in yout form named „xfa“, isn't it? I this way the result „null“ is correct.The correct script should propably be:this.resolveNode("ChildSubform.MyTextfield").rawValueHere's a very good explaination of how the resolveNode() and resolveNodes() methods work: resolveNode...

You better use a set of edit patterns to allow multiple ways to enter a date instead of bothering users everytime with a message box. Here's a example: LiveCycle Blog: Flexible Datumseingabe durch Datumsmuster//Flexible input of dates with date patterns

Hi Lucas, not really except by printing the form created with Designer with the Adobe PDF printer as a new PDF and then editing this PDF with Adobe Acrobat again.

An AcroForm is a form created with Adobe Acrobat instead of LiveCycle Designer. It is compatible with Adobe Reader on iOS and Android. But an AcroForm is not dynamic. It's just a static PDF with form fields and scriptings.

There was one Service Pack (SP1) with some enhancments before Designer was pushed into AEM Forms.LiveCycle Help | What's New in LiveCycle ES4 Service Pack 1