Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

subform1 overflowing in to subform2

Avatar

Former Community Member
                                                                     
                                                                    
Hi i am new to lIVE cYCLE, and i am currently trying to design a simple form ,

which has two subforms, and each subform just has as text field in it.

say

subform S1
S1_TEXT

SUBFORM S2
S2_TEXT

I am doing all this in the design view of LC,

SUBFORM s1 and S2 are dynamic, i mean they are supposed to expand or contarct based o the data in the xml


here comes my problem,

i have placed the text_field "s1_text" and did "wrap in subform" and did the same for s2_text.

but now s1 overflows in to s2

i did checked :

allow multiple lines,

expand to fit (y)

and also saved it as dynamic xml form,

and also i have noted that

for subforms s1 and s2

the PAGINATION TAB is not highlighted

and also the flow direction field is not highlighted.

can anybody please help me to find out what is wrong in my approach.

Thanks


1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The parent that contains subform1 and subform2 must be set to flowed.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The parent that contains subform1 and subform2 must be set to flowed.

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