Hello Tamas,

We've decided to reopen this ticket and change it to a Feature Request. Extending the grid's excel export functionality to work with columns whose width isn't set in pixels is an ongoing internal discussion. I've edited the opener post with some ideas as to how this might work. Please note that we haven't fleshed out any concrete details yet, but we've agreed to reopen this item and track the demand for it. Based on the number of votes and other factors feature requests get included in our backlog and in future releases.

Regards,
Lachezar Georgiev
Progress Telerik

Hi Tamas,

Doing that would make it impossible to customize at a later stage when an event (or other approach) is implemented. The grid must not make such changes on its own, and when a way to customize the export is implemented, you will have a neater hook to do that than the workaround I posted.

Regards,
Marin Bratanov
Progress Telerik

Hi Tamas,

In a future version it is possible that an event before the export is exposed that would let you perform such customizations. The grid should not, on its own, change your settings. The export of the grid takes the settings you defined for the grid and uses them as much as possible. Another option you can consider is creating the file with your own code, you can see an example in my post from 13 Jan 2020  here.

Regards,
Marin Bratanov
Progress Telerik

Hi Tamas,

The "rem" or "em" units (such as other valid CSS units like "vw") are not something that is valid for Excel, so it cannot read them and thus - the width of those columns becomes invalid. This is, however, not something the grid should touch, because it cannot know what your expected conversion would be.

With that said, I can recommend setting your column widths in pixels or percent.

Other options are:

• Vote for and Follow a programmatic method to export so you can swap the widths with your code, export, then swap them back to those special units: https://feedback.telerik.com/blazor/1470774-trigger-grid-excel-export-from-code.
• Try this workaround that relies on multithreading to achieve the same effect:
  the command button gets a click handler

  <GridCommandButton OnClick="@SetColWidth" Command="ExcelExport" Icon="@IconName.FileExcel">Export to Excel</GridCommandButton>

  and that handler does that work:
  

      string ColWidth { get; set; } = "10rem";
  
      async void SetColWidth()
      {
          ColWidth = "100px";
  
          // tweak this to be slightly lager then the typical time the exprot will take
          // the idea is to have the widths change, this method starts ticking and waiting
          // the multithreading allows the grid to export with the pixel widths
          // this timer ticks out and restores the desired widths
          // Note: this will not work for WASM, because it only has a single thread at the time of writing
          await Task.Delay(1000);
  
          ColWidth = "10rem";
          StateHasChanged();
      }

  on columns that use the variable for their width, something like this (based on my previous sample):
  

      <GridColumns>
          <GridColumn Field="@nameof(SampleData.ProductId)" Title="ID" Width="@ColWidth" />
          <GridColumn Field="@nameof(SampleData.ProductName)" Title="Product Name" Width="@ColWidth" />
          <GridColumn Field="@nameof(SampleData.UnitsInStock)" Title="In stock" />
          <GridColumn Field="@nameof(SampleData.Price)" Title="Unit Price" />
          <GridColumn Field="@nameof(SampleData.Discontinued)" Title="Discontinued" />
          <GridColumn Field="@nameof(SampleData.FirstReleaseDate)" Title="Release Date" />
      </GridColumns>

With all that said, I am marking this as something that needs a different approach as it is not a bug in the component, but a behavior of Excel and how web development cannot apply directly to it.

Regards,
Marin Bratanov
Progress Telerik

Hi Tamas,

Can you reproduce this on our demo or with the code from our docs? I am asking, because I tested both and the file opens as expected for me. I am also attaching a small project with the docs sample so you can test it and compare against the problematic one that you have. If this does not help you resolve this, please modify this project to show the problem and send it back to me.

In the meantime, I suggest running a repair on your Office installation and also testing other files downloaded from the Internet - it is possible that some security feature/setting/issue is blocking data display and proper file manipulation on the actual OS, not in the Telerik-generated file.

Regards,
Marin Bratanov
Progress Telerik