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

Dynamic Drop down

Avatar

Level 2

I am trying to create a drop down menu with lets say groups that populate a second drop down menu with certian people in them. Can someone please point me in the right direction for this?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Here is a sample I put together for you. The code is on the exit event of the 1st DDList. If you have numerous options in that list you may want to look at a different code construct (Select in Javascript).

Paul

View solution in original post

4 Replies

Avatar

Former Community Member

This is doable but where is the information that will populate the DDLists come from? Are you going to hard code it into the form?

Paul

Avatar

Level 2

Yeah, it needs to be hardcopied into the form. Is that possible?

Avatar

Correct answer by
Former Community Member

Here is a sample I put together for you. The code is on the exit event of the 1st DDList. If you have numerous options in that list you may want to look at a different code construct (Select in Javascript).

Paul

Avatar

Level 2

Thank you so much! That worked perfectly! You just made my week.

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