In a non Telerik 3rd-party tool we can export to Excel, and groups that have been defined will be rendered with group buttons in Excel that can be expanded and collapsed in the Excel spreadsheet. With Telerik when we export a RadGrid that has a user-defined group, there are no grouping expand/collapse buttons in the generated Excel spreadsheet.

Related Telerik Support ID: 758667

Thanks.

Hi,

in Radgrid header context menu filter section would be nice the possibility to add field to filter and change the logical operator (AND / OR ).

Best Regards

For the time being the following workaround can be used:

CSS:

    <style>
        .RadGrid_Default .RadButton_Simple input {
            border: 0 none;
        }
    </style>

ASPX:

        <telerik:RadGrid ID="RadGrid1" runat="server">
            <MasterTableView>
                <Columns>
                    <telerik:GridTemplateColumn UniqueName="EditColumn" AllowFiltering="false">
                        <HeaderStyle Width="70px" />
                        <ItemTemplate>
                            <telerik:RadButton ID="rbEdit" runat="server" Text="Select" Skin="Simple"
                                AutoPostBack="false">
                            </telerik:RadButton>
                        </ItemTemplate>
                    </telerik:GridTemplateColumn>
                </Columns>
            </MasterTableView>
        </telerik:RadGrid>

where Simple is the name of the used Skin.

Since Q3 a change in the client-side binding of the GridTemplateColumn has been introduced. The column no longer automatically populates controls in the ItemTemplate. The change is result of an optimization in code regarding the virtualization and batch editing features of the grid. The new behavior is far more optimized and ensures much faster and robust operation of the control in various cases of client-side binding.

If I'm to believe the Telerik agent in this forum thread... http://www.telerik.com/community/forums/reply-thread.aspx?messageId=0&threadId=750553

then presenting users WITHTEXTTHATLOOKSLIKETHIS (as is done by default in Metro Skin Grid Filter Menu) is a "design" feature. I happen to believe that menu items ought to be readable by human users and not appear like they are the result of some sort of keyboard malfunction... at least by default. If some "designer" out there feels the need to present their users with ABSURDTEXTFORMATTING, then it is they that should be required to implement some sort of hack, not the rest of us. This was a horrible design decision made by someone at Telerik, and the fact that I am required to appeal to other developers who have better things to do with their time in order to get Telerik to see the absurdity of this design and fix it is most troubling.

Enable drag-and-drop between cells

I would like to see the RadGrid control have support for a global header and footer template row for the entire grid.

The header or footer would be rendered within a row inserted at the top or bottom of the grid, with styling consistent with the grid's skin.  It would actually be very similiar to CommandItemTemplate, but could be used with the default command rows and would apply to the very top and bottom of the grid, and not be part of the MasterTableView.  It would simply be to anchor something to the top or bottom of the grid with a consistent look, feel, and width of the rest of the grid.

<TELERIK:RadGrid Runat="server">
<HeaderTemplate>
Whatever I want to put here would be placed in it's own row at the very top of the grid and it would be automatically styled consistent with the Grid's skin.  I could put controls in here and they would bubble through the grid (and it's AJAX functionality, if anything is enabled). 
</HeaderTemplate>
<MasterTableView ... />
<FooterTemplate>
Same here, except it goes at the bottom of the grid.
</FooterTemplate>
</TELERIK:RadGrid>

In the example image I attached, the bottom row with "Primary Service Completed" is not actually part of the grid, but we used some CSS to make it look like it was... but that particular CSS is fragile if we ever changed the global skin on the site or for the Grid in particular.  That is what I might want to put in the FooterTemplate.