Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

page breaks

Avatar

Former Community Member

I am creating muli-page applications which require short answers & long answers. I can't get text boxes to carry over to the next page and have the rest of the information flow down.  I have marked "Allow Page Breaks" in the subforms and Object palette. I am attaching what I have done on my first application.

Thanks,

Donna

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

We can't see your form while it is queued ....in the mean time make sure that your root subform is flowed and that your form is saved as dynamic.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

We can't see your form while it is queued ....in the mean time make sure that your root subform is flowed and that your form is saved as dynamic.

Paul

Avatar

Former Community Member

Thank you so much.  I had not saved it as a Dynamic form.

Donna

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