Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

"Add More" input to dropdown list

Avatar

Level 2

Hello,

I was having some difficulty trying to customize this dropdown list to a format very similar to one of the dropdown options on ebay.

The cell is blank and has a drop down. Once you click the drop down, you will find the following

relaxed

straight leg

__________

other

When you click "other," the field box now contains the  text that reads " Enter a Specific Value." and you are able to add in whatever text you want in the field

That would be great if there was a way in LiveCycle to do something close to or exactly like this.

thanks

-vargs

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

1) allow custom text entry

2) add exit event

// form1.page1.dd::exit - (JavaScript, client)


if (this.rawValue == "Other") {

  this.rawValue = "Enter a specific value";

}

3) add entry event
// form1.page1.dd::enter - (JavaScript, client)

if (this.rawValue == "Enter a specific value") {
  this.rawValue = "";
}
Steve

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

1) allow custom text entry

2) add exit event

// form1.page1.dd::exit - (JavaScript, client)


if (this.rawValue == "Other") {

  this.rawValue = "Enter a specific value";

}

3) add entry event
// form1.page1.dd::enter - (JavaScript, client)

if (this.rawValue == "Enter a specific value") {
  this.rawValue = "";
}
Steve

Avatar

Level 2

Works perfectly.

Thanks a lot 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] ----