--- title: Configuring UI data export related: - https://docs.kentico.com/13/managing-website-content/exporting-data-from-the-user-interface.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). This page explains how to customize the [Excel and CSV export](https://docs.kentico.com/13/managing-website-content/exporting-data-from-the-user-interface.md) for data in the Xperience administration interface: ## Customizing Excel export templates You can customize the default appearance of exported XLSX templates. On each export, the system searches for a _Template.xlsx_ file in the following locations within the administration project: 1. **\~\CMS\App\_Data\CMSModules\DataExport\\\\\Template.xlsx** 2. **\~\CMS\App\_Data\CMSModules\DataExport\\\Template.xlsx** 3. **\~\CMS\App\_Data\CMSModules\DataExport\\\Template.xlsx** 4. **\~\CMS\App\_Data\CMSModules\DataExport\Template.xlsx** The system searches for the templates according to the listed priorities. This means that when exporting listings of an object type on a specified website, the path stated in 1. is searched first. If the _Template.xlsx_ file is not found there, location 2 is searched and so on. This allows you to add dedicated templates for each object type and website in your system. The _DataExport_ folder is NOT present in the administration project by default. You need to create the folder and all required subfolders manually to use custom templates. The __ folder name must be identical to the name of the exported file, e.g. _cms\_user_ for user listings as the exported file name is _cms\_user.xlsx_ (the actual object type name is _cms.user_, but dots are replaced with underscores in file names). The __ folders are only searched when exporting site-related objects. > **Note:** For objects that can be both global (shared among all sites in the system) and site-related, such as [roles](https://docs.kentico.com/13/managing-users/role-management.md), we recommend adding the _Template.xlsx_ file to both the site and global folders. Such objects use the global or site-related export template, depending on the selected user interface or the type of the user doing the export (global template for global administrators, site-related template for standard users). > **Info:** If the _Template.xlsx_ file is not found in any of the locations, the default template is used. The same happens if the template is opened for editing at the time of export or if the current user does not have the Read and Write permissions for the template file (on the operating system level). ### Custom data export folder Excel export templates can also be stored in a different location than the default _\~\App\_Data\CMSModules\DataExport_. The custom location can be defined by adding the following key to the _AppSettings_ section of the _web.config_ file: ```html ``` For the value of the key, you can either use a local disk path (for example, _C:\MyDataExportTemplates_) or a UNC path (for example, _\\\server1\MyDataExportTemplates_). Using a UNC path may be useful in cases when you want to share the same templates between several Xperience instances running on separate servers. ### Template format The template spreadsheet can contain any graphics, text or any other pre‑filled data in it, while the following macros can be used in any cells. On export, the macros are replaced with the actual exported data: - **##HEADER##** – replaced with the header row. When advanced export is used, it is only replaced if the **Export header row** option is enabled. - **##DATA##** – replaced with the actual exported data. - **##TABLE##** – replaced with both the header row and the exported data. - **{%WhereCondition%}** – replaced with the WHERE condition used for export (only relevant when exporting via the **Advanced export** dialog). - **{%OrderBy%}** – replaced with the ORDER BY expression used to order exported items (either the expression configured in the **Advanced export** dialog or the default column according to which records are sorted when exporting using the **Export to Excel** action). - **{%TotalRecords%}** – replaced with the total number of exported records. - **{%ObjectType%}** – replaced with the type of the exported object (e.g. _cms.userlist_). You can also use all standard Context (data) [macros](https://docs.kentico.com/13/macro-expressions.md) the same way as you are used to within Xperience administration interface. So for example, if you create a _Template.xlsx_ file and upload it to _\~\App\_Data\CMSModules\DataExport\cms\_user\\_... ![Example of an XLSX template](https://docs.kentico.com/docsassets/13/configuring-ui-data-export/template_example.png "Example of an XLSX template") ... the XLSX file with exported users will be structured accordingly. ![Example of an exported XLSX file](https://docs.kentico.com/docsassets/13/configuring-ui-data-export/export_example.png "Example of an exported XLSX file") ## Customizing CSV delimiters CSV is an abbreviation for [Comma-separated values](http://en.wikipedia.org/wiki/Comma-separated_values). It is a file format that stores tabular data in text form – each line represents one row of data, while particular values (columns) in each row are separated by a comma (,) or a semicolon (;). The comma is used as a column delimiter by default if you select the **Export to CSV** action, while you can choose between the comma and the semicolon in the **Advanced export** dialog. The choice of the correct delimiter depends on your operating system's regional settings. If you use an inappropriate delimiter, **data from each row will be displayed in a single cell**, as the displaying software (for example, Microsoft Excel) will not be able to identify the boundaries between individual values. ![Incorrect CSV delimiters](https://docs.kentico.com/docsassets/13/configuring-ui-data-export/csv_inappropriate_delimiter.png "Incorrect CSV delimiters") If an appropriate delimiter is used, **data from each column will be displayed in individual cells** as expected. ![Correct CSV delimiters](https://docs.kentico.com/docsassets/13/configuring-ui-data-export/csv_appropriate_delimiter.png "Correct CSV delimiters") ### Delimiter settings on operating system level To find out which delimiter you should use in your environment or to configure your system to use the other one than the one currently used: 1. Go to **Start menu -> Control Panel** in Windows. 2. Open the **Clock, Language, and Region** settings category. 3. Click the **Region and Language** category. - The Region and Language dialog opens on the **Formats** tab. 4. Click **Additional settings...**. - The **Customize Format** dialog opens on the **Numbers** tab. 5. Here you can choose the delimiter in the **List separator** field. ![](https://docs.kentico.com/docsassets/13/configuring-ui-data-export/image2013-11-6.png) - The separator chosen here is the one that you should use when exporting listings data in order to get it displayed correctly. 6. If you made any changes, click **OK** in the **Customize format dialog** and also click **OK** in the **Region and Language** dialog.