Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.
Watch Now!

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Add button

Avatar

Former Community Member
9/22/09 2:24:19 PM

When using subform instance control:add, I have info that starts on the bottom of one page and the rest is as the top of the next page. I am trying to get the info from both pages wrapped into one subform so that my "add" button will add everything. Is this possible?

Views

850

Replies

2

Total Likes

Translate
Translate
1 Accepted Solution

Avatar

Correct answer by
Former Community Member
9/23/09 7:48:30 AM

In Design view your subform cannot span pages. You will have to get them on the same page.

Paul

View solution in original post

Views

463

Replies

0

Total Likes

Translate
Translate
Jump to reply
2 Replies

Avatar

Correct answer by
Former Community Member
9/23/09 7:48:30 AM

In Design view your subform cannot span pages. You will have to get them on the same page.

Paul

Views

464

Replies

0

Total Likes

Translate
Translate
Jump to reply

Avatar

Former Community Member
9/23/09 8:11:59 AM

Thank you Paul, I finally figured that out.

Views

469

Replies

0

Total Likes

Translate
Translate
Related Conversations
Lifecycle Designer, add instanses to table Solved

Views

1.6K

Likes

0

Replies

3
How to allow deselecting "multiple" radio buttons via a function Solved

Views

1.2K

Likes

0

Replies

2
Live Cycle 2 Email Submit Button Solved

Views

725

Likes

0

Replies

2
Presence of buttons in subform due to their position Solved

Views

621

Likes

0

Replies

1
PDF.JS adds basic XFA support

Views

1.8K

Likes

3

Replies

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