This is a migrated thread and some comments may be shown as answers.

[Solved] DetailTable appears even though disabled

5 Answers 149 Views

Grid

This is a migrated thread and some comments may be shown as answers.

Carl asked on 24 Sep 2009, 03:14 AM

I have a RadGrid hierarchy with a MasterTable and a number of DetailTables. Most of the DetailTables display normally as expected.

However, two of the DetailTables as GridTableViews have been disabled with the properties Enabled="false" Visible="false" in the markup of the *.ascx user control with the RadGrid. Even so, they still appear!!!!! I had the same problem when I tried disabling them in codebehind (remembering to do the rebind in the prerender).

How can this be? Are the Enabled and Visible properties not operational server side in markup or in code-behind? Is it really necessary to disable each of the individual columns in the DetailTable? Is that the only solution? Or is this a bug? And it should be possible to disable the entire DetailTable?

5 Answers, 1 is accepted

answered on 24 Sep 2009, 04:49 PM

I have now also tried to disable with additional properties as follows with this markup:

                <telerik:GridTableView runat="server" DataSourceID="sdsNSecondaryDirectoriesWrite" DataKeyNames="InternalKey"
                    CommandItemDisplay="Bottom" CommandItemSettings-AddNewRecordText="Add new SecondaryDirectory"
                    Enabled="false" Visible="false" ExpandCollapseColumn-Display="false" RowIndicatorColumn-Display="false">

Note that I have now set four different properties to "false" including Enabled, Visible, ExpandCollapseColumn-Display and RowIndicatorColumn-Display.

Even so, I have been unsuccessful in disabling this DetailTable and it continues to display and operate as if I had never set any of those properties to false. It is as if those properties are completely useless and non-operational.

answered on 25 Sep 2009, 03:39 PM

Well it's now very confusing because I received a separate email from you saying that the problem would be fixed.

Also it does not make sense that it is "expected" because Telerik has many control behaviors that allow both server-side managemenet as well as client-side management. In this case, I do NOT want to leave it to client-side management. I want to manage it on the server-side and completely disable generation of the DetailTable depending on various conditions server-side.

So what is the correct property to set so that server-side generation of the DetailTable is disabled?!?

answered on 28 Sep 2009, 05:47 PM

I have re-read again the documentation at

http://www.telerik.com/help/aspnet-ajax/grdenabledconventions.html

and will continue to express my opinion that this does not make sense. If it is an intentional design with expected behavior, then it is a design that is inconsistent, confusing, and unnecessarily complicated. In other words, if there is a simple property "Enabled" that is supposed to work on server-side, then it should operate as a simple binary switch: the grid has "Enabled = true" and the grid is on and enabled, or else the grid has "Enabled=false" and the grid is off and disabled.

If this property is to be meaningful and operational server-side, then why should I have to mess with changing a whole bunch of other properties client side? That seems to me to be an unnecessarily complicated programming model. If I disable a grid server side, especially as I want to do for one of several detail tables of a master table, then I shouldn't have to do anything with the clientside properties of the disabled detail table because the disabled detail table should NOT even be generated server side and thus not even appear client side.