Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Problem getting fields to break across pages

Avatar

Level 1

I have been working on developing a form that must meet the following criteria:

Multiple user input text fields that must be able to break across pages.

Multiple users must be able to save the document with their individual inputs included, the result being a single .pdf with multiple signatures.

I have a workaround in mind for the multiple input part. I can't get the text fields to break across pages. Any help is appreciated.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Make sure that you save the form as a dynamic form. Also the root container of the subform must be set to flowed for it to reflow. It can contain a positioned subform inside of it but the root must be flowed.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Make sure that you save the form as a dynamic form. Also the root container of the subform must be set to flowed for it to reflow. It can contain a positioned subform inside of it but the root must be flowed.

Paul

Avatar

Level 1

Thanks Paul, it worked perfectly!

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] ----