Expand my Community achievements bar.

SOLVED

Flowed subform not breaking properly at page break

Avatar

Level 2

An example illustrating my problem is attached.

The problem:

I have a positioned subform, page breaks allowed.

On the right this (main)subform contains an expandable (notes) text input object, page breaks allowed.

On the left, it contains a flowable subform, page breaks allowed. This subform contains a (step) subform with an expandable text input object, page breaks allowed. The user can create copies of the step subform.

If the user enters enough text in the notes field to force a page break, things work fine. Part of the text is on one page, and the remainder is on the following page, in the correct horizontal position (under the text of the preceeding page).

However, if the user either creates enough copies of the step subform to force a page break, or fills one of the step fields enough to force a page break, ALL steps, and the right notes field are sent to the top of the next page.

How do I force the break to appropriately divide the content of BOTH the left and right portions of the main subform? That is, to leave the appropriate steps on each page, and the appropriate part of the notes text on each page?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Unfortunately if you break across a page you cannot go back and change the layout of a previous page. So the columns do not act independantly as you need them to (as they are under the same parent subform).

Paul

View solution in original post

6 Replies

Avatar

Former Community Member

Are the steps and the Notes independant of each other or is it a one to one mapping where for each step there is a corresponding Note?

Paul

Avatar

Level 2

The notes are independent of the steps.  That is, there may be many steps, but only one notes field.

Avatar

Correct answer by
Former Community Member

Unfortunately if you break across a page you cannot go back and change the layout of a previous page. So the columns do not act independantly as you need them to (as they are under the same parent subform).

Paul

Avatar

Level 2

Thanks, Paul. At least I can now stop my futile experiments

Avatar

Level 10

John Brinkman just posted an article about displaying parallel columns of text on the FormFeed blog. Don't know if it will help or not!

http://blogs.adobe.com/formfeed/2009/06/displaying_parallel_columns_of.html

Avatar

Level 2

Thank you. I have downloaded the article and will work through it.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----