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 entry already selected is displayed in the text field. When you select the pushbutton, a list with all possible values is displayed.

Example of Use

If you want to create a table with dropdown lists, whereby each table row has the same values in its dropdown list, you should use DropDownByKey. This is also usually more efficient than DropDownByIndex.

To ensure Accessibility a check is made during design time that the label property has been specified.

If no label has been set, and no descriptive text has been specified for the appropriate bound context element in the ABAP Dictionary, a check is made for the tooltip property.

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.

When using a dropdown list box, always display this UI element alongside a label to ensure accessibility.

 

Runtime Class

CL_WD_DROPDOWN_BY_KEY

 

Properties in the View Designer

Name	Type	Initial Value	Bindable
ID	STRING	(automatic)	No
enabled	WDY_BOOLEAN	true	Yes
Explanation	Text		No
keyVisible	WDY_BOOLEAN	false	Yes
readOnly	WDY_BOOLEAN	false	Yes
selectedKey	STRING		mandatory
state	WDUI_STATE	normal	Yes
textDirection	WDUI_TEXT_DIRECTION	inherit	Yes
tooltip	Text		Yes
visible	WDUI_VISIBILITY	visible	Yes
width	STRING		Yes

 

Events in the View Designer

Name

onSelect

Further properties that can be inherited are defined in the associated higher-level class.  The associated interface elements are:

●      AbstractDropDownByKey 

●      AbstractDropDown 

●      UIElement 

●      ViewElement 

Dynamic Programming

For dynamic programming the same properties, events, and aggregations are provided 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	ENABLED	WDY_BOOLEAN
Explanation	EXPLANATION	WDY_MD_TRANSLATABLE_TEXT
keyVisible	KEY_VISIBLE	WDY_BOOLEAN
labelFor	LABEL_FOR	STRING
readOnly	READ_ONLY	WDY_BOOLEAN
selectedKey	SELECTED_KEY	STRING
state	STATE	WDUI_STATE
state: normal	CL_WD_DROPDOWN_BY_KEY=>E_STATE-NORMAL
state: required	CL_WD_DROPDOWN_BY_KEY=>E_STATE-REQUIRED
textDirection	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	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_DROPDOWN_BY_KEY=>E_VISIBLE-NONE
visible: visible	CL_WD_DROPDOWN_BY_KEY=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

 

Dynamic Programming of Events

View Designer Name	Runtime Name
onSelect	ON_SELECT

Example

You can find examples of this interface element in the system in the Web Dynpro application WDR_TEST_UI_ELEMENTS, and in the component WDR_TEST_EVENTS in the view DropDownByKey.