Hello Ed,

Surely, technically we can add a built-in DropDownList editor, but the number of required additional parameters will defeat the purpose - the code will be as bulky, as if you add an EditorTemplate with a component inside. Moreover, the EditorTemplate provides complete flexibility with regard to

• Which component to use, including one that is not ours
• When, how and what to update in the original data item
• Let's not forget scenarios that may require custom data-binding or virtualization. Unlike the ASP.NET AJAX controls, the Blazor components do not communicate with the data layer directly.

Regards,
Dimo
Progress Telerik

Hi Ed,

Are you asking about a foreign key column or you just need a dropdown with a collection of choices during editing?

For the first assumption - we prefer not to have this as a built-in feature for multiple reasons, related to our Blazor components' architecture and the fact that they are decoupled from the data. So, if you have this scenario, bind the <GridColumn> to the foreign key ID, and then use templates for editing, filtering, etc., as in the linked KB article.

For the second assumption - use an EditorTemplate, as in the linked example.

Generally, we recommend developers to adjust the model to the Grid API, which in some cases may mean flattening data in a Grid view model. Doing the opposite may not always produce the best results in terms of developer experience (e.g. too much templating in the foreign key column scenario).

Regards,
Dimo
Progress Telerik