Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

duplicate textfields in footer

Avatar

Former Community Member

We have a form that requires a footer with a number of fillable fields.  I'd like to configure the form so that changes to the values on any page are reflected throughout the document.  I read about something called "duplicate fields" in Acrobat, but can't seem to find the equivalent functionality in LiveCycle Designer ES2.  Can you please point me in the right direction?

Thank you!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

FYI - what worked for me in the end was to set the binding to "Use Global Data" on the footer fields that I want to change globally.

View solution in original post

3 Replies

Avatar

Level 7

I would recommend setting that on the master page.

Click on the Hierarchy Palette then Untitled Content Area (that's the default name).

With the content area highlighted, you can resize the content area to give room for a footer.

Then, anything you put in the the footer will change for every page.

Avatar

Former Community Member

Thank you for the quick reply.  I tried something similar - I added a subform called "Footer" in the PageArea1 Master Page and included the fields in the subform.  I thought ContentArea1 was for non-header/footer content.  Currently the textfields in the Footer subform don't reflect values across pages.  Is that the magic of the "ContentArea"?

Avatar

Correct answer by
Former Community Member

FYI - what worked for me in the end was to set the binding to "Use Global Data" on the footer fields that I want to change globally.

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