Expand my Community achievements bar.

SOLVED

expandable text field expnds well, but does not go to the second page, why?

Avatar

Former Community Member

hello

after hours of work and reading blogs, I was able to create a form with multiple expandable fields.

the problem is they dont go to the second page. they will be cut and sometimes everything moves to a second page and I have a blank first page.

please help.

I need to mention it happens when I'm using tables in my forms. simple text will over flow to next page just fine.

it just the problem when there are tables

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Send the form and a description of the issue to LiveCycle8@gmail.com and I will have a look when I get a chance.

Paul

View solution in original post

4 Replies

Avatar

Former Community Member

Did you allow the page break in the Table subform?

Paul

Avatar

Former Community Member

Hi ,

Yes

It is checked.

the issue is that if the box expands to the end of the page, not only it will not go to the next page also it will move entirely to the second page so it leaves a big blank space behind in first page and you missing the end of the test as well.

I need to make it overflow to next page without moving from first page.

I have all subforms flowed and allowed to break as well as table and rows.

any other suggestions?

Thaks for taking this question Paul.

Avatar

Correct answer by
Former Community Member

Send the form and a description of the issue to LiveCycle8@gmail.com and I will have a look when I get a chance.

Paul

Avatar

Former Community Member

I put everything together again and

it works okay now.

thank you for your help.

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