Right from the start I get following errors in den Dircect Window:
System.ArgumentNullException: Value cannot be null. (Parameter 'nullableType')
at System.ArgumentNullException.Throw(String paramName)
at System.Nullable.GetUnderlyingType(Type nullableType)
at Telerik.Blazor.Common.Filter.FilterOperatorFactory.GetFilterOperatorsForType(Type type, ITelerikStringLocalizer localizer)
at Telerik.Blazor.Components.Common.BoundColumnBase.ThrowIfInvalidDefaultFilterOperator()
at Telerik.Blazor.Components.Common.BoundColumnBase.OnParametersSet()
at Microsoft.AspNetCore.Components.ComponentBase.CallOnParametersSetAsync()
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at Telerik.Blazor.Components.Common.ColumnBase.SetParametersAsync(ParameterView parameters)
I can not load any Grid anymore. The error shows:
System.ArgumentNullException
Value cannot be null. (Parameter 'nullableType')
I think it has something to do with "DefaultFilterOperator" but I cannot figure out it myself
With 5.1.1 everything works just fine.
2 Answers, 1 is accepted
Rank 1
Iron
It seems like this issue is caused when there is a GridColumn with parameter "Field" set to a value that is not a property of the grid item model. Before 6.0.0 this was possible and did not cause an exception.
I have created a small example that lets you reproduce the error.
To reproduce just let the unit test run for one of the configurations v5 or v6. With v5 the test succeeds, with v6 it does not.
I hope this helps to fix the issue.
Hi all,
Thank you very much for your cooperation!
The behavior is caused by a regression in the Grid that you may track here: [Regression] Filterable Grid throws if a column field is not bound to a field from the model.
The workaround I'd suggest is to set the FieldType of the column.
Regards,
Nadezhda Tacheva
Progress Telerik
Hi Hendrik,
We haven't received reports for such an issue so far. To move forward with the investigation, please provide an isolated runnable sample that reproduces the problem. This will allow me to debug it and find the root cause.
Thank you in advance for your cooperation!
Hi Ryan,
Can you provide a minimal reproducible example, so we can debug this? You may include some dummy data and mimic your exact Grid configuration.
I am getting the same issue on one of the grids in our Blazor WASM app, after upgrade.
Error goes away if I set FilterMode to None, which is not a fix
Hi all,
I am not able to confirm the root cause without a reproduction but I suspect the issue may be related to a regression that we had in 6.0.0 related to filtering nullable types.
It has been fixed and we released a patch version a couple of days ago. Can you please upgrade to 6.0.2 and test again? If the issue persists, please provide an isolated sample that reproduces it, so we can investigate further.