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

limit the max char for Dropdown list

Avatar

Level 2

How is it possible to limit the editing of a drop-down list, if the drop down list is configured as editable. Thank you.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Can't be done in script .... the events that fire when the dropdown is being typed into do not work the same way.

The only way I can get this is using the exit event add this javascript code:

Where 5 is the length of the string that you will allow. The user can type in a long string, then it will warn them and truncate to the required length.

Paul

View solution in original post

5 Replies

Avatar

Former Community Member

There is nothing exposed in the UI to do that. You may be abel to do it through script.

Paul

Avatar

Level 2

How to do it in script? Is it possible stop the user from entering once the max number of character is reached? Thanks...

Avatar

Correct answer by
Former Community Member

Can't be done in script .... the events that fire when the dropdown is being typed into do not work the same way.

The only way I can get this is using the exit event add this javascript code:

Where 5 is the length of the string that you will allow. The user can type in a long string, then it will warn them and truncate to the required length.

Paul

Avatar

Level 2

Thank you. In this way the user can happily enter as many characters as they like and upon exit then the words will be truncated.

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