Expand my Community achievements bar.

SOLVED

How to position form title on second page of flowed form

Avatar

Level 5

Good day All;

Well, I think I am getting a small understanding of how to create forms.

What I have is a form that “might” span more than one page. This is what I have.

The form has 4 sections that are able to expand as either text is entered or additional row are added.

On the “master” page I have placed the form “title”. When I added the “title” to the “master” page, it put the title in the correct place on the first page. When I added rows so the form would span 2 pages, the “title” was in the correct place, but, the added row was placed over top of the “title”.

I have added sub forms along with the “title” to the master page with the same result. I am thinking that there must be a way to add the title to the second (or more) pages without having the added text overwrite the title.

Thanks All

Chomp

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The master page has a content area (the purple dashed line). This marks the area where content will be placed from the normal pages. If you place the

Title outside of this content area then you will not have an overflow condition.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The master page has a content area (the purple dashed line). This marks the area where content will be placed from the normal pages. If you place the

Title outside of this content area then you will not have an overflow condition.

Paul

Avatar

Level 5

Thanks Paul, worked like a charm

Chomp

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