Expand my Community achievements bar.

SOLVED

positioned subfield wrapped in flowed subfield not page breaking

Avatar

Level 1

I have a text field in a positioned subform. that subform is in a flowed subform. I want it to break on to the next page, but it just flows off the bottom of the page without adding a new page and even goes over my master page footer items.

all items are set to allow page breaks. text box is set to allow multiple lines and fit to y.

It works when I get rid of the positioned subform, however I want that subform so i can have other elements side by side with the text field and maintain the layout.

I read in here that "The field can be in a positioned subform, but its parent must be flowed (it might be different than the page subform)."

why isn't this working for me

here is the link http://www.grantwalker.info/box/test.pdf

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The untitled subform that the message and the checkbox are located in must be set to autofit in theY direction on the Layout tab. You set the field to autofit but not the subform that it is housed in (the positioned subform).

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The untitled subform that the message and the checkbox are located in must be set to autofit in theY direction on the Layout tab. You set the field to autofit but not the subform that it is housed in (the positioned subform).

Paul

Avatar

Level 1

Amazing, Thank you! these forums are so helpfull.

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 81, 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 81, column 5] ----