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

another subform problem

Avatar

Former Community Member

I am working on a very simple form which I need one section (2 pages long) to be repeatable. I have done repeating subforms before on several other forms but this one keeps rendering the max number of instances of the flowed subform no matter what I try to get it to show only the initial single instance.

The form is a flowed subform which has 6 positioned subforms and one addtional flowed form (sectionII) which needs to repeat.

I need it to display a single instance when the form is opened. I have a simple button that the click event has script to add another instance. Structure is below. Not sure where I'm going wrong on this. Any suggestions will be greatly appreciated.

structure1.JPG

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Awww darn! Figured it out.

For anyone having a similar issue....dont forget to check for "DUH" items.

Form properties were defaulted to 7.0 and higher. Saw lots of warnings in the Report Pallette! Always forget that is there.

Changed the form to 8.0 and higher and voila...fixed. !

Sometimes it helps to put things away and go have a beer.

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Awww darn! Figured it out.

For anyone having a similar issue....dont forget to check for "DUH" items.

Form properties were defaulted to 7.0 and higher. Saw lots of warnings in the Report Pallette! Always forget that is there.

Changed the form to 8.0 and higher and voila...fixed. !

Sometimes it helps to put things away and go have a beer.

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