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

side by side expanding subforms

Avatar

Level 4

I know that in order for a subform to have dynamic elements it in, it needs to be flowed, and the form itself needs to be flowed. So, is there a way to put two flowing subforms side by side? I want to have two columns in my form, but I want each column to be flowed and dynamic.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

After you add the page ...make your Page subform flowed and set the "Place" parameter in the Pagination section of the object palette to the Content Area that you want. I modified the sample ....I also renameed the Content Areas to make it easier to identify them.

Paul

View solution in original post

5 Replies

Avatar

Former Community Member

Yes ...on your master page you will need to have two Content Areas defined. Now you can define it so that when the 1st content area is full it will beigin filling the secoond content area.

Paul

Avatar

Level 4

Thanks, Paul. I really appreciate how speedy you are with your assistance!

OK, so I set up the content areas on my master page, but now I can't access the design view. It's only letting me create elements on the Master page. I'm sure I am missing a simple step here. I attached my form.

Avatar

Level 4

Actually, what is happening is that when I add a new page, it's only letting me access one content area on that page(the bottom left one).

Avatar

Correct answer by
Former Community Member

After you add the page ...make your Page subform flowed and set the "Place" parameter in the Pagination section of the object palette to the Content Area that you want. I modified the sample ....I also renameed the Content Areas to make it easier to identify them.

Paul

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