Prathap, upon further exploration, the error I was hitting when filtering on Nulls triggered the following error inside Syncfusion's "SfDropDownBase.cs"...
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=Syncfusion.Blazor.DropDowns
StackTrace:
at Syncfusion.Blazor.DropDowns.SfDropDownBase`1.Search(String inputValue, IEnumerable`1 items, String filterType, Boolean ignoreCase) in Syncfusion.Blazor.DropDowns\SfDropDownBase.cs:line 542
However, the good news is that I may have found what I'll call a compromised (but successful) workaround for the issue. To explain...
Instead of the example offered in https://blazorplayground.syncfusion.com/embed/BXVTCNMDJKgWLmsU?appbar=true&editor=true&result=true&errorlist=true&theme=bootstrap5, imagine the following sample Model declaration:
public class MyClass
{
public int ID { get; set; }
public string? Name { get; set; }
}
Now, with the above Model in mind, imagine that in my database table there are 3 records. In those records, the 'Name' field values happen to be...
Record 1: Name="Hello World"
Record 2: Name=""
Record 3: Name=Null
Given the above Model, when my filter is based on "Name", no error will occur in SfDropDownBase.cs when handling Records #1 and #2 above. However, the Syncfusion error I've listed will occur at Record #3.
After close study, my compromise workaround for this issue turns out to be based on my having altered MyClass in the following manner...
public class MyClass
{
public int ID { get; set; }
public string? Name { get; set; } = string.Empty
// Notice above that I have now supplied 'Name' with a default value.
}
Once I did the above, the problem went away.
Prathap, in retrospect I can now see what was the issue here and it makes sense. Though this is going to be a significant task, I am even willing to conform the rest of my code to that discovery. That said, if an SfGrid's filtering process requires me to provide a default value for every property in every Class/Model, then I would offer the following respectful suggestion...
Syncfusion may want to make the fact that this is a requirement something that is stated prominently and explicitly in the SfGrid's support pages. In other words, preferably, one should not have to infer such a thing from sample code. (If all of this is indeed explicitly expressed on those page's, I am sorry, but I missed it).
If you have any more feedback to provide on this... including the time-saving possibility of my only having to supply default values to Model properties of String datatype... please do not hesitate to let me know. Thank you.
