Unplanned
Last Updated: 13 Feb 2026 08:38 by ADMIN
David
Created on: 05 Feb 2026 18:27
Category: UI for Blazor
Type: Feature Request
1
Add IValueConverter usage from WPF in Blazor columns

Draft feature request (copy/paste)

Title: Add per-column value converters (WPF-style) to Telerik Blazor Grid columns

Product: UI for Blazor → Grid
Type: Feature Request

Description:
In Telerik UI for WPF, grid column definitions can reference a converter by name (e.g., IValueConverter) to transform values for display without writing a custom cell template for each column.

In Telerik UI for Blazor Grid, templates are currently the primary way to change how values render in a column (which works, but becomes repetitive across many columns/grids).

Request:
Add a column-level conversion API that allows specifying a converter/formatter function for display (and optionally editing). Example concepts:

  • Converter="nameof(MyConverters.StatusToText)"

  • or DisplayConverter="(item) => …" / ValueFormatter="Func<TItem, object, string>"

  • optionally ConvertBack-like support for editing scenarios (or separate EditConverter)

Why this is needed:

  • Reduces repeated <Template> markup for simple formatting/transformations

  • Centralizes formatting/conversion logic in reusable code

  • Improves maintainability and consistency across grids

  • Eases migration for teams coming from Telerik WPF where converters are a common pattern

Use cases:

  • Enum/int → user-friendly text

  • Boolean → “Yes/No”, icons, badges

  • Null/empty → placeholder text

  • Code → display name (via lookup)

  • Domain-specific formatting shared across many grids

Workarounds today:

  • Column <Template> or computed properties (both valid, but not as concise/reusable for large grids)

  • Extracting RenderFragments can reduce repetition, but still requires templating infrastructure for what is logically a simple conversion step

Expected behavior:

  • Converter applies consistently anywhere the column renders (cell, export if applicable, etc.)

  • Works with sorting/filtering in a predictable way (ideally sorting/filtering still uses raw field value unless explicitly configured)


 

1 comment
ADMIN
Dimo
Posted on: 13 Feb 2026 08:38

Hello David,

Thanks for the detailed description of your request. I am confirming it as valid, but with an important caveat to keep in mind.

IValueConverters and TypeConverters are a standard and common approach in WPF apps, because the framework itself provides the foundations for using them. Blazor does not have the same infrastructure in place, which means that the enhancement relies on more research and implementation from us, that needs to be justified by enough customer demand. It may also turn out that the feature may impose a performance penalty on the app, which is highly undesirable.

So, IValueConverter can make a lot of sense for developers coming from the WPF world, but the same approach may not necessarily make the same sense in Blazor.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.