Grid Troubleshooting on Editing
Environment
| Product | Progress® Kendo UI® Grid for jQuery |
Description
This article provides solutions for issues you might encounter while working with the editing functionality of the Grid.
- Setting null values for foreign key columns leaves a column value blank
- Changing the MultiSelect value when used as a custom editor does not trigger the save event of the Grid
- Editing Boolean columns renders styles improperly
Setting null values for foreign key columns leaves a column value blank
Normally, a foreign key column is bound to a numeric data field which points to the unique keys of a separate collection. If some of the values in the foreign key column are null, an issue related to editing might occur. While such issues do not affect the display mode, they mislead the column editor by indicating that it has to handle object values instead of primitive values. As a result, when a value is picked from the MultiSelect, the widget sets an object value to the data item of the Grid (for example, {text: "Foo", value: 3}) instead of a numeric value (for example, 3) which causes the Grid cell to remain blank upon exiting the edit mode.
To work around the issue, use either of the following approaches:
- Use zeros instead of nulls to match the data values with the declared data field type.
- Use a custom column editor with a manually configured DropDownList that has a
valuePrimitivesetting set totrue.
For a runnable example on implementing foreign-key columns in the Grid, refer to this demo.
Changing the MultiSelect value when used as a custom editor does not trigger the save event of the Grid
When a Kendo UI MultiSelect is used as a custom editor in the Grid and the value of the MultiSelect is changed, the save event of the Grid is not triggered. The reason is that the value of the MultiSelect is a reference type (array) which prevents the normal usage of the model.set() function for setting the value of the corresponding model property.
To work around this issue, define a custom data-binding mechanism. After applying this fix, the save event of the Grid is properly triggered each time a new selection is added to the value of the MultiSelect. For a runnable example, refer to the article on using the MultiSelect as a custom editor in the Grid.