How i gave custom color to excel sheet header and group header ?

Couldn't you write an access method to generate some kind of xml representation of all filters in place so that could be sent back to the server to generate the excel export?

Here was my complete implementation of CSV export using the ServiceStack.Text and Json.Net libraries. This maybe helpful to some people :]

//ServiceStack.Text library (https://github.com/ServiceStack/ServiceStack.Text)
//Json.Net library (http://json.codeplex.com)

/***** Controller Action *******/

        public FileContentResult CourtDateSearchResultToCsv(string searchResultJson)
        {
            List<CourtCalendarQueryRecord> searchResult = Newtonsoft.Json.JsonConvert.DeserializeObject<List<CourtCalendarQueryRecord>>(searchResultJson);
            string csv = "";
            if (searchResult != null)
            {
                //covert all datetime values to proper date string for before conversion.
                var formatResult = searchResult.Select(o => new
                {
                    CourtCaseNumber = o.CourtCaseNumber,
                    ScheduledDate = o.ScheduledDateTime.ToShortDateString(),
                    ScheduledTime = o.ScheduledDateTime.ToString("hh:mmtt"),
                    HearingType = o.HearingType
                });
                
                //serialize objects collection to csv string
                csv = ServiceStack.Text.CsvSerializer.SerializeToString(formatResult);
            }
            byte[] csvBytes = ASCIIEncoding.ASCII.GetBytes(csv);
            return File(csvBytes, "text/csv", "CourtDateSearchResultData.csv");
        }


/***** VIEW *******/

<script type="text/javascript">

		function doCourtDateCsvExport(){
			var resultJsonData = $("#CourtCalendarGrid").data("tGrid").data;
			if (resultJsonData.length > 0) {
			    if ($.browser.msie == true) //fix IE min-date serialization issue
			        $("#CourtCalendarGrid_searchResultJson").val( JSON.stringify(resultJsonData).replace(/01-01-01T08:00:00Z/gi, "0001-01-01T08:00:00Z") );
			    else
			        $("#CourtCalendarGrid_searchResultJson").val(JSON.stringify(resultJsonData));

				$("#CourtCalendarGrid_CsvForm").submit();
			}
			else {
				alert("Sorry, there is no data to export.");
			}
		}
		
</script>


@(Html.Telerik().Grid<CourtCalendarQueryRecord>()
    .ToolBar(toolBar => toolBar.Template(
        @<text>
				<button class='t-button t-button-icon t-button-bare' title='Export to Excel' onclick='doCourtDateCsvExport()' > <img src='/images/icons/application_go.gif' alt='' />Export To Excel </button>                           
        </text>
    ))
    .Name("CourtCalendarGrid")
    .Sortable(sorting => sorting.SortMode(GridSortMode.SingleColumn))
    .DataBinding(dataBinding => dataBinding.Ajax().Select("_GetCourtCalendar", "Home", new { forCurrentUser = ViewBag.ForCurrentUser}).OperationMode(GridOperationMode.Client))
    .Columns(columns =>
    {
        columns.Bound(o => o.ScheduledDate).Title("Date").Width(120).ClientTemplate("<#= ScheduledDateDisplay #>");
        columns.Bound(o => o.ScheduledTime).Title("Time");        
        columns.Bound(o => o.CourtCaseNumber).Title("CR Number");
        columns.Bound(o => o.ClientName).Title("Client Name");
    })
)

<form method="post" action="@Url.Action("CourtDateSearchResultToCsv", "Search")" id="CourtCalendarGrid_CsvForm")">
	<input type="hidden" name="searchResultJson" id="CourtCalendarGrid_searchResultJson")" />
</form>

It is fairly easy to implement, using .Net MVC, create a controller action like this: 

[ValidateInput(false)]
        [HttpPost]
        public ActionResult XLSHandler(string html)
        {
            try
            {
                string h = HttpUtility.UrlDecode(html);
                string filename = DateTime.Now.Ticks.ToString() + ".xls";
                System.Text.UTF8Encoding encoding = new System.Text.UTF8Encoding();
                return File(encoding.GetBytes(h), "application/vnd.ms-excel", filename);
            }
            catch (Exception e)
            {
                //handle error
                return View();
            }
        }

Then in your javascript you should create a hidden form, and when they click the export button, populate the input on the form with the HTML from the grid, then submit the form to the controller action:

function exportGrid(){
        var h = $("#grid").html();
        $("#html").val(h);
        $("#myForm").submit();
    }

<form id="myForm" action="@Url.Action("XLSHandler", "Report")" method="post">
<input type="hidden" id="html" name="html" />
</form>

Actually, I think all the tools are almost there:
1. First the developer creates an Excel/Word document and saves it as Office XML.
2. The developer puts kendoui template placeholder in the XML.
3. The JS app will load the template with Ajax and then apply the JSON values to it.

The only missing part is a way to offer this endresult to the user... For example, I wouldn't know how to set a content-type header in a new window with JavaScript.

An alternative would be to create a server-side component with the same Office XML templates and to let KendoUI send its data to the server which will then set the content-type and content-disposition headers for downloading the file.

I guess you would need a server side end point (MVC controller or otherwise) that would take all the current grid data in JSON (or XML) and then be responsible for generating and sending the resulting Excel file back to the client?

All you need to do is convert the JSON from the grid into CSV http://stackoverflow.com/questions/4130849/convert-json-format-to-csv-format-for-ms-excel

Shouldn't be too hard to create the server side wrappers in various platforms. It will make it really hard to replace grid based apps built with Datatables, Jqgrid or  most other grids on the market. For me this means the grid will most likely only be usable for front-end purposes. All of my clients are used to being able to export the data seen in the grids. Even the beta Datatables provides a plugin for multiple export formats.

This is meat and potatoes...so to speak for developing custom web apps, CMS and other admin functionality. I hope the dev team is not going to dismiss this as too difficult as it would likely limit the grids use in serious apps.

If you generated the xml with javascript(which I know is possible), you could leave it up to us to do what we need to do with it..

Off the top of my head, I could see a javascript method post to another page that basically takes in the xml and offers it back to the user to download.. Seems a little redundant, but it would get the job done..

Please reconsider this..