Feature Request: Built‑in Excel Export Support for Fluent UI Blazor Grid

[VigneshElysyan]

Summary

I am requesting a built‑in Excel Export feature for the Fluent UI Blazor FluentDataGrid.
In many real‑world applications, grids require export functionality, and currently developers need to depend on external Excel libraries to achieve this.

Background & Problem

In my project, I have multiple grids (N number of grids), and each grid requires an Excel export option.
I have created the Grid as a shared component, but the Excel export code cannot be shared, because each grid has different columns and export structures.
This results in:
Duplicate code in many places
Difficulty maintaining export logic
Extra dependency on external libraries
More time needed to implement for each grid

A built‑in Fluent Blazor Excel export functionality would significantly simplify this scenario.

Why This Feature is Needed

Each grid has unique columns, so writing export logic repeatedly is inefficient.
Most modern UI libraries (like Syncfusion, Telerik, DevExpress) provide native Excel export capabilities.
A built‑in export option improves developer productivity and avoids reliance on 3rd‑party Excel libraries.
Enables consistent, reliable, and optimized export behavior across all grids.

Requested Feature

Please add native Excel export support to FluentDataGrid, including:

Export all columns
Export selected or visible columns
Support for header text
Support for custom formatting (numbers, dates, currency, etc.)
Ability to override/extend export behavior for custom scenarios

Kind Request

This feature would save a lot of development time and improve the Fluent Blazor ecosystem.
Kindly consider adding this enhancement in upcoming releases.
Thank you for your hard work and support!

[vnbaaij]

Hi,

Thank you for your suggestion, but we have no plans on adding this feature anytime soon. We are only a small team and this would take a hefty amount of time to implement. Also, I do not consider this a part of the Core functionality.

There is also the community components project. If you are willing to work on this yourself, it could perhaps be offered as an addition through that extension.

[VigneshElysyan]

@vnbaaij Thanks For You Reply !

[vnbaaij]

Sure, no problem! Moving this to th discussion area so it stays visible to others as well.