To set the value, apply any of the following approaches:
- Use the
valueproperty. If the value is set through the
valueproperty, you have to hook up to the
valueChangeevent and manually update the value of the
- Use the
ngModelvalue binding. If the value is set by the
ngModelvalue binding, the framework automatically will update the corresponding field from the model after the value of the component changes.
- Use the
formControlNamevalue binding available in the Reactive forms. If the value is set by the
formControlNamevalue binding, the framework automatically will update the corresponding field from the form model after the value of the component changes.
- The MultiSelect does not support the simultaneous usage of the
valueproperty and the
- The MultiSelect does not support values which contain
\nnew line characters. The regular
inputHTML DOM element which the MultiSelect uses internally treats
\nas a regular whitespace. Therefore, when the component compares the value of the
inputelement with the data item that is selected by the user, the two values differ, the value of the
inputelement is actually not present in the data of the component, and the MultiSelect does not recognize it. To handle such issues, map the incoming data so that it contains regular whitespaces only.
When binding the MultiSelect value, the component provides options for:
- Using primitive values (string, number, or other)
- Using complex values (objects)
- Using primitive values from object fields
- Handling invalid value errors
If the MultiSelect is bound to a dataset of primitive values, its value will be an array of primitives of the same type.
If the MultiSelect is bound to a dataset of objects, its value will be an object of the same type.
When the selected item is an object, always specify
valueField. If you do not a set value for the field, the MultiSelect will compare the items by reference, which may complicate debugging. For example, the selected value will not be applied, if it does not reference the exact passed
If the MultiSelect is bound to a dataset of complex objects and the
valuePrimitive property is set to
true, its value will also be of the primitive type (string, number).
If the value which is assigned through the
In the following example, the component has both its
[textField] specified, which implies that the
[data] will contain objects. Because the
[valuePrimitive] is not explicitly set to
- Change the value type, or
- Update the settings of the component.
The following table lists the valid configuration scenarios.
|[primitives]||primitives||Not set (automatically calculated as |
|[objects]||objects||Not set (automatically calculated as |