Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Can I bind multiple field values to a single field?

Avatar

Level 2

Here's the scenario:  I have a form with 2 pages.  On the first page, there are three fields for a person's first, middle, and last name.  On the second page, there's a field that just says "Name".  I want the user to fill out the first, middle and last name fields, and then have the "name" field on the second page reflect all three fields from the first page.  How can I accomplish this?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Add client-side script to the calculate event on the name field on page 2 to concatenate the name fields on page 1. For JavaScript, something like this:

this.rawValue = form1.page1.subform1.firstName.rawValue + " " + form1.page1.subform1.lastName.rawValue;

Steve

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Add client-side script to the calculate event on the name field on page 2 to concatenate the name fields on page 1. For JavaScript, something like this:

this.rawValue = form1.page1.subform1.firstName.rawValue + " " + form1.page1.subform1.lastName.rawValue;

Steve

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