Skip to content

Commit 6e50dca

Browse files
chore(grid): clarify primitive types for binding
1 parent 76b3548 commit 6e50dca

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

components/grid/columns/bound.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ You can use the following properties on the bound columns:
9292
## Notes
9393

9494

95-
* For advanced operations such as grouping, filtering, sorting, you *must* set a `Field` to the column, and the field it points to must be a primitive type.
95+
* For advanced operations such as grouping, filtering, sorting, you *must* set a `Field` to the column, and the field it points to must be a string or a value type (such as a number, string, DateTime, boolean).
9696
* If a `Field` is not set the column will not allow filtering, grouping, sorting and editing for the column.
9797
* If the `Field` points to a custom object or something like an `IDictionary`, errors will be thrown upon those actions because there are no known data operations on non-primitive types in .NET. An alternative is to implement all data source operations yourself by handling the [OnRead event](../manual-operations).
9898
* To bind to nested (complex) models (also called navigation properties), use only the name of the field that holds the child class and its own field. For an example, see the [Bind to navigation properties in complex objects]({%slug grid-use-navigation-properties%}) article.

0 commit comments

Comments
 (0)