!--a11y-->
DropDownByKey 
A DropDownByIndex UI element provides the user with a dropdown list box. You cannot select more than one entry from the selection list. The UI element consists of a text field, a button, and a selection list. Any list item already selected is displayed in the text field. When the user chooses the pushbutton, a list of all possible values is displayed.
If you want to create a DropDown list in which some entries are available in multiple, use DropDownByKey.

To enable the
development of
accessible
applications the label property is checked during the syntax
check.
If no label has been set, and no descriptive text has been specified for the appropriate bound context element in the ABAP Dictionary, the tooltip property is checked.
Examples of the Display
|
|
|
The dropdown list
box UI elements, DropDownByKey and DropDownByIndex,
do not differ from each other when displayed on the screen. However, the data binding model for the
DropDownByKey UI element has a completely different concept. See
Data Binding
within Web Dynpro generally, and
Data Binding of UI
Element Properties and
Data Binding of a
Dropdown Listbox. You can
find more information about using dropdown listboxes with index data binding
in
AbstractDropDownByKey.
Runtime Class |
Properties in View Designer
Name |
Type |
Initial Value |
Bindable |
ID |
STRING |
(automatic) |
no |
WDY_BOOLEAN |
true |
yes |
|
Translatable text |
|
no |
|
WDY_BOOLEAN |
false |
yes |
|
STRING |
|
no |
|
WDY_BOOLEAN |
false |
yes |
|
STRING |
|
Mandatory |
|
WDUI_STATE |
normal |
yes |
|
WDUI_TEXT_DIRECTION |
inherit |
yes |
|
Translatable text |
|
yes |
|
WDUI_VISIBILITY |
visible |
yes |
|
STRING |
|
yes |
Events in View Designer
Name |

Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:
For dynamic programming, the same properties, events and aggregations are available as in the View Designer. Bear in mind the different spellings.

Note that when you program value lists dynamically in context (NODE_INFO->SET_ATTROBUTE_VALUE_SET() ), that you have to insert a CONDENSE if you use integer types for an attribute.
Dynamic Programming of Properties
View Designer Name |
Runtime Name |
Type |
ENABLED |
WDY_BOOLEAN |
|
EXPLANATION |
WDY_MD_TRANSLATABLE_TEXT |
|
KEY_VISIBLE |
WDY_BOOLEAN |
|
LABEL_FOR |
STRING |
|
READ_ONLY |
WDY_BOOLEAN |
|
SELECTED_KEY |
STRING |
|
STATE |
WDUI_STATE |
|
state: normal |
CL_WD_DROPDOWN_BY_KEY=>E_STATE-NORMAL |
|
state: required |
CL_WD_DROPDOWN_BY_KEY=>E_STATE-REQUIRED |
|
TEXT_DIRECTION |
WDUI_TEXT_DIRECTION |
|
textDirection inherit |
CL_WD_DROPDOWN_BY_KEY=>E_TEXT_DIRECTION-INHERIT |
|
textDirection ltr |
CL_WD_DROPDOWN_BY_KEY=>E_TEXT_DIRECTION-LTR |
|
textDirection rtl |
CL_WD_DROPDOWN_BY_KEY=>E_TEXT_DIRECTION-RTL |
|
TOOLTIP |
WDY_MD_TRANSLATABLE_TEXT |
|
VISIBLE |
WDUI_VISIBILITY |
|
visible: none |
CL_WD_DROPDOWN_BY_KEY=>E_VISIBLE-NONE |
|
visible: visible |
CL_WD_DROPDOWN_BY_KEY=>E_VISIBLE-VISIBLE |
|
WIDTH |
STRING |
|
Dynamic Programming of Events
View Designer Name |
Runtime Name |
ON_SELECT |
There is a system example for this UI element in the DEMO_UIEL_STD_SELECTION component in the DEMO_UIEL_DROPDOWN_BY_KEY application.