Clicking filter icon in column header sorts column and shows filter dropdown.

I have a SfGrid that has filtering & sorting enabled for my columns. When I click on the default filter icon that shows in the column header, it will also trigger the sort event.  See the video attached in zip file. 

I was unable to find demos of columns that have both filtering & sorting applied. So I am unsure what the expected functionality is here. But, from a user perspective I believe this should not be happening. I should be able to click the filter icon to show the filter popup; and if i click any other area of the header it would sort the values in the column.  It appears that both the filter icon and the column header are using the same clickable space.

My data source is a List<ExpandoObject> populated from a view model.

I am trying to determine if this is a bug with my code, or the syncfusion control(s). I am using version 19.1.0.59 of the blazor syncfusion nuget package.
My grid code looks like the following:

var toolbarItems = new List<string>
{
    "ColumnChooser"
};
<SfGrid @ref="dataGrid"
        ID="Grid"
        GridLines="GridLine.Both"
        DataSource="@ViewModel.Data"
        ShowColumnChooser="true"                        
        AllowGrouping="true"
        AllowSorting="true"
        AllowMultiSorting="false"
        AllowPaging="true"
        AllowReordering="true"
        AllowFiltering="true"
        Toolbar="@toolbarItems"
        Width="1270">

    <GridFilterSettings Type="Syncfusion.Blazor.Grids.FilterType.CheckBox"></GridFilterSettings>
    <GridPageSettings PageSizes="new int[] { 10, 15, 20, 25, 50, 75, 100, 250 }" PageSize="50" />

    <GridColumns>
        @foreach (var field in ViewModel.Fields)
        {
            if (!Enum.TryParse(field.DataType, out ColumnType columnType))
                columnType = ColumnType.String;

            <GridColumn IsPrimaryKey="@field.PrimaryKey"
                        AllowSearching="true"
                        ShowInColumnChooser="@field.Show"
                        Visible="@field.Show"
                        HeaderText="@field.DisplayName"
                        Type="@columnType"
                        AutoFit="true"
                        MinWidth="120"
                        Format="@field.Format"
                        Field="@field.Key" />
        }
    </GridColumns>
</SfGrid>

Attachment: Syncfusion_Grid,_Sort__Filter_Issue.mp4_d5134015.zip

3 Replies 1 reply marked as answer

RS Renjith Singh Rajendran Syncfusion Team June 2, 2021 10:11 AM UTC

Hi Drew, 

Greetings from Syncfusion support. 

We checked this scenario by creating a sample based on the shared codes, but we could not face the reported problem with the sample from our side. We are attaching the sample and video demo for your reference, please download the attachments from the link below, 

Kindly refer the above attachments and if you are still facing difficulties, then the following details would be helpful for us to proceed further. 

  1. Share a simple issue reproducing sample for us to validate based on your scenario.
  2. Or if possible, reproduce the problem with the above attached sample and share with us for further analysis.
  3. Share the exact scenario you are facing this reported problem.

The provided information will help us analyze the problem, and provide you a solution as early as possible. 

Regards, 
Renjith R 



DF Drew Frisk June 2, 2021 09:25 PM UTC

Hi Renjith,

After much debugging and comparing, I was able to reproduce the issue in the sample project you provided. 

Specifically, this is what I changed to result in the issue:

  • The blazor server app is using dotnet core 3.0
  • The bootstrap version is 3.3
  • The syncfusion theme is bootstrap, NOT bootstrap4.

I attached the updated sample.

Attachment: ServerApp_6cc59fa8.zip


RS Renjith Singh Rajendran Syncfusion Team June 4, 2021 03:30 AM UTC

Hi Drew, 

We have analyzed the shared sample. This problem is occurring only because of older dot net version. We checked this scenario, by upgrading to dotnet version 5 and tried reproducing the reported problem. We could not face this reported problem with latest dotnet version. So, we suggest you to upgrade to dotnet version to overcome the reported problem.  

We are also attaching the upgraded dot net version sample for your convenience, please download the sample from the link below,  

Please get back to us if you need further assistance.  

Regards,  
Renjith R 


Marked as answer
Loader.
Up arrow icon