Hi René,

The FieldType is used when:

• you have grouping and you also use the OnRead event: https://docs.telerik.com/blazor-ui/components/grid/manual-operations#grouping-with-onread
• you are using ExpandoObjects: https://github.com/telerik/blazor-ui/tree/master/grid/binding-to-expando-object
• you are using a DataTable as the data source: https://demos.telerik.com/blazor-ui/grid/data-table

Essentially, it's there so you can tell the grid what the type of the data is when there isn't a way for it to infer the type from the data source.

To filter enums, you must use enum fields, or a custom filter that converts the enum to the underlying field type.

Regards,
Marin Bratanov
Progress Telerik

Hi René,

The FIeldType and the actual type of the column must match. While that could, in some situations, get hacked for an enum and int for the basic filtering modes, I would not recommend it.

The situation with the checklist filter is more complex - it takes the options from the grid data (uses Distinct). Thus, the grid can put in the checkbox list only what you put in its data - and that's an integer now, not an enum.

Thus, you should bind that column to an enum field in order to get the proper filtering, grouping and sorting behavior. If you want more fields to use the same value, you should define them in the model (they could be integers too), and their getters/setters should properly tie them to the enum field they actually describe. Or, you could perform such additional operations only when and where they are needed - e.g., in UI, view-model or in the database only.

Lastly, if you want to keep using an integer with a checklist filter, but to have "meaningful" text for the options, you should build your own filter menu that resembles a checklist, you can find examples in our documentation.

Regards,
Marin Bratanov
Progress Telerik