I can't seem to get the proper results with an enum filter if I manually page data to a grid.  I have a grid attached to a table with one column containing an Enum.  This grid was initially setup to read the entire db table into an array bound to the grid.  In this configuration, the Enum drop down filter works properly.  However, if I modify the structure so that it uses manual paging with DataEnvelope I get an error in the browser when selecting a drop down item as shown..

blazor.webassembly.js:1 System.InvalidOperationException: The converter specified on 'Telerik.DataSource.FilterDescriptor.Value' is not compatible with the type 'FulfillmentModule.Shared.Models.SRStatus'.

Any suggestions as to what I'm doing wrong?

Hi Marin,

it's awesome that this feature is available now.

For all those who want to implement a localized dropdown like I needed to do, you can take a look at the following code (It's attached as zip file as well):

 

@using System
@using System.Collections.Generic
@using System.Threading.Tasks
@using Telerik.Blazor.Components
@using Telerik.Blazor
@using Telerik.DataSource

<TelerikGrid Data="@this.UserData" Pageable="true" Sortable="true" FilterMode="GridFilterMode.FilterRow">
<GridColumns>
<GridColumn Field="@(nameof(User.Id))" Title="@this.Localizer["Id"]" />
<GridColumn Field="@(nameof(User.ClientType))" Title="@this.Localizer["ClientType"]">
<FilterCellTemplate>
@{
this.FilterCellContext = context;
<TelerikDropDownList Data="@this.ClientTypes" TextField="Text" ValueField="Value" Enabled="true" @bind-Value="this.SelectedClientType" OnChange="@this.OnClientTypeChanged">
</TelerikDropDownList>
}
</FilterCellTemplate>
<Template>
@{
var item = context as User;
<div>@this.Localizer[item.ClientType.ToString()]</div>
}
</Template>
</GridColumn>
</GridColumns>
</TelerikGrid>

@code {
public class User
{
public Guid Id { get; set; }

public ClientType ClientType { get; set; }
}

public enum ClientType
{
Normal,
Special
}

public class ComboBoxData<T>
    {
        public T Value { get; set; }

        public string Text { get; set; }
    }

protected override async Task OnInitializedAsync()
{
foreach (ClientType clientType in Enum.GetValues(typeof(ClientType)))
{
this.ClientTypes.Add(
new ComboBoxData<ClientType>
{
Value = clientType,
Text = this.Localizer[clientType.GetDescription()]
});
}
}

protected async Task OnClientTypeChanged(object state)
{
var filter1 = this.FilterCellContext.FilterDescriptor.FilterDescriptors[0] as FilterDescriptor;

if (filter1 == null)
{
return;
}

filter1.Value = this.SelectedClientType;
filter1.Operator = FilterOperator.IsEqualTo;
this.FilterCellContext.FilterDescriptor.LogicalOperator = FilterCompositionLogicalOperator.And;
await this.FilterCellContext.FilterAsync();
}

    protected IEnumerable<DtoReadUser> UserData { get; set; }

protected List<ComboBoxData<ClientType>> ClientTypes { get; set; } = new List<ComboBoxData<ClientType>>();

    protected ClientType SelectedClientType { get; set; }

    protected FilterCellTemplateContext FilterCellContext { get; set; }

[Inject]
    protected IStringLocalizer<Users> Localizer { get; set; }
}

 

Best regards,

Christian

Thanks for the enum filter!

I second Christian's extended request: Localization of enums (or any other objects) would be super; not only for the grid's filter but also for DropDownList, ComboBox, etc.

Currently I'm trying to wrap enums in a tiny view model where I have a text property which gets its value from an attached localizer.

It would be helpful if we could localize individually per-component. Individually, because the text of an enum can differ based on the context it is displayed in.
Maybe via a localizer or a localization function, or an scenario specific identifier to be used with a global per-type localizer, or a mixture of those?

Thanks so much for releasing this!

We have desperately been waiting for this feature.

Regards,

René

Thanks, Marin

 

Could you please confirm that filter will be compatible with OData? E.g.

someProperty eq MyApp.Sex`Male`

 

Thanks

I'm really looking forward to this.

Excellent. Thank you, Marin.

 

 

I agree with Peter, this is a serious issue. I love Blazor and the control that it gives as well as the excellent performance but I am now considering having to revert to my old development toolset: CodeOnTime for producing a data maintenance application. I'm gutted - but a consistent UI is essential.

This is *really* hurting us now. We've had a complaint from management that we are unable to filter on transaction statuses (which is essential) without having to have an inconsistent user-interface (which is a poor user experience and is confusing users).

Critical bugs in existing components should be addressed before the development of new components.

 

I cannot stress enough how important it is for us to have the ability to filter enum values, whilst maintaining a standard look throughout the app (i.e. the filtering is done in the grid, not next to it).

It's also very important that the OData filter works with it too. I thought this was a bug, not an omission. Please make it high priority, this basic need is for more common than some of the more fancy features being added.

"Unplanned"? REALLY? This is essential in a modern web app.

The competition has it already: https://demos.devexpress.com/blazor/GridFilterRow

Having a separate drop-down filter outside the grid means that there are two different ways of filtering the data and you have to explain to customers/users why this is so and then again as to why some columns are filtered this way and others are not.

Please implement this, and an Excel-style of multi-selection using a dropdown list with check-boxes.

Regards,

Paul

I *really* need enum filtering too.

 

Also, when I open the filter menu, and then scroll my page down so the filter menu disappears, I get the following exception:

blazor.webassembly.js:1 WASM: Unhandled exception rendering component:
l.printErr @ blazor.webassembly.js:1
put_char @ dotnet.js:1
write @ dotnet.js:1
write @ dotnet.js:1
___syscall4 @ dotnet.js:1
(anonymous) @ wasm-00d61dde-538:1
(anonymous) @ wasm-00d61dde-4447:1
(anonymous) @ wasm-00d61dde-2434:1
(anonymous) @ wasm-00d61dde-2432:1
(anonymous) @ wasm-00d61dde-4362:1
(anonymous) @ wasm-00d61dde-5668:1
(anonymous) @ wasm-00d61dde-6199:1
(anonymous) @ wasm-00d61dde-1432:1
(anonymous) @ wasm-00d61dde-635:1
(anonymous) @ wasm-00d61dde-4992:1
(anonymous) @ wasm-00d61dde-3248:1
(anonymous) @ wasm-00d61dde-1328:1
(anonymous) @ wasm-00d61dde-337:1
(anonymous) @ wasm-00d61dde-2630:1
(anonymous) @ wasm-00d61dde-5927:1
(anonymous) @ wasm-00d61dde-5588:1
(anonymous) @ wasm-00d61dde-6199:1
(anonymous) @ wasm-00d61dde-1432:1
(anonymous) @ wasm-00d61dde-635:1
(anonymous) @ wasm-00d61dde-4992:1
(anonymous) @ wasm-00d61dde-3248:1
(anonymous) @ wasm-00d61dde-1328:1
(anonymous) @ wasm-00d61dde-438:1
(anonymous) @ wasm-00d61dde-1737:1
(anonymous) @ wasm-00d61dde-3497:1
Module._mono_wasm_invoke_method @ dotnet.js:1
call_method @ dotnet.js:1
(anonymous) @ dotnet.js:1
beginInvokeDotNetFromJS @ blazor.webassembly.js:1
l @ blazor.webassembly.js:1
e.invokeMethodAsync @ blazor.webassembly.js:1
value @ telerik-blazor.js:1
value @ telerik-blazor.js:38
value @ telerik-blazor.js:38
(anonymous) @ telerik-blazor.js:38
(anonymous) @ telerik-blazor.js:38
Show 11 more frames
blazor.webassembly.js:1 WASM: Microsoft.JSInterop.JSException: Unknown edit type: 0

We need this feature to filter enum values as well. (I have already voted for it).

I don't know if this is related or already planned, but what if one wants to localize the enum values in the filter (and the grid as well)? Is this already possible using a converter (that inherits from IValueConverter) like it can be done e.g. in WPF?

 

Best regards,

Christian

I think a complete implementation should contain:

For enumeration values:

* Filter: combo box with enumeration values with item checkboxes to allow filter on one or more enumeration values

* Display: name of enumeration value

* Editing: Single selection combo box (filterable by input nice to have)

For enumeration flags

* Filter: combo box with enumeration values with item checkboxes to allow filter on one or more flags

? Display: list of flags (e.g. comma separated)

* Editing: Multi selection combo box

 

Important issue for me, too. Please also consider a meaningful input in form of a combo box, too.