Hello Nitesh,

I see your point and we are discussing the scope of this task now.

Regards,
Dimo
Progress Telerik

Hi,

After inspecting the request, it turns out that exposing additional export options might be useful for some concrete basic scenarios, but covering more general scenarios (read below) will be hard to configure by the developer.

For example, if there is an option to configure which columns and data should be exported, then the Telerik Blazor Grid component will not be necessary - in fact, this functionality can be achieved even outside of the Blazor framework as the exported columns and data may not be even present in the Grid - they can be any other columns and data.

Suppose that there is some kind of a helper class that allows exporting any data to an Excel file:

var exportedData = TelerikBlazorExportHelper.ExportToExcel(new TelerikExcelExportOptions() 
{ 
  FileName = "excel-export.xslx"
  Columns = new List<ColumnDescriptor>() 
  { 
    new ColumnDescriptor()
    {    
      Field = "ProductName" 
      ...
    }
  ...
  },
  Data = ...
})

In addition, more complex scenarios with the Grid will require passing additional arguments that are not trivial for the developer to configure - consider a grouping scenario, where aggregates should be calculated for the given data set, their names should be localized, etc.

Regards,
Stamo Gochev
Progress Telerik