As my colleague has already advised, we have exposed different events and modifications to the Export functionality which you can utilize to achieve your behavior. The samples are made to work in the most common scenarios and for more specific setups you need to apply some additional logic.
The approach for exporting custom headers with the ExportToXlsx
method is similar to the one when using the older export method. The only difference is that the ExportToXlsx utilizes the ElementExportingToDocument
event instead of the ElementExporting
sender, GridViewElementExportingToDocumentEventArgs e)
&& e.Value.GetType() ==
e.Value = (e.Value
As for the error
you are receiving, unfortunately, we cannot reproduce such issue from our side. My advice is to raise a ticket with a sample so we can have a more detailed look and advise you.
William, I would like to once again point out that most of this information is available in the online documentation of the Export functionality. Please have a look at it to see the difference between the methods and respectively the events they expose.
Telerik by Progress
Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin
, a suite of polished and feature-rich components for the Xamarin framework, which allow
you to write beautiful native mobile apps using a single shared C# codebase.