Exporting is performed using client-side API in browsers. However, some browsers (including IE8, IE9 and Safari on Mac OS) do not implement an API for saving files, thus the exporting feature will not work correctly without the use of additional services. Refer to the Set up Server-side Proxy section for details.

When export is enabled, an Export button is displayed above the grid.

Pressing this button, an end user can export grid data in the required format.

When a possibility to export only the currently selected rows is needed, set the export | allowExportSelectedData option to true. End users will be given a choice of whether to export the total grid or selected rows only.

Export to Excel

The dxDataGrid widget exports data to excel as it is presented in the grid - with sorting, filtering and grouping applied. Data types in the resulting Excel file are kept - numbers stay numbers, dates stay dates. This allows users to work with the exported data in Excel without any data transformations. For instance, users can use the exported data in Excel formulas, summaries, etc.

NOTE

Take into account the limitations related to Excel possibilities when exporting grid data to Excel.

While the dxDataGrid widget supports any number of nesting levels in data grouping, the range of possible nesting levels in Excel is from 0 to 7.

Set up Server-side Proxy

If your application will be used in browsers that do not implement an API for saving files (for instance, IE8, IE9 and Safari on Mac OS) and you need the exporting feature to work correctly, you can implement a server-side proxy, which will stream the file back to the end user in response to a POST request. The proxy implementation is different for each platform.

ASPx

If your server runs the ASP.NET web application framework, you can implement a proxy using the following HTTP handler.