Scenario:
I have a grid that will specify a default GroupByExpression when it is first loaded. The default expression is a compound expression such as the following:
ReportGroup1 [Group 1], ReportGroup2 [Group 2] Group By ReportGroup1, ReportGroup2
A GroupByExpression is created with this string and added to the MasterTableView of the grid.
Then after the page loads, drag another column, such as LastName, to the group by panel. Now I have two GroupByExpressions.
Problem:
I first noticed the problem when I went to remove the LastName column from the group by panel. Everytime I would do this, it would always remove the first item in the group by panel, which was my original expression.
After taking a closer look, i noticed that the _createGroupPanelItems jscript function in the GridGroupPanel.js file is not creating the items with the correct HierarchicalIndex - which is then passed down in the postback as the index to remove from the group by panel.
As a temporary workaround, I have broken up the default expression to be two expressions, and it appears to be working as expected.
I have a grid that will specify a default GroupByExpression when it is first loaded. The default expression is a compound expression such as the following:
ReportGroup1 [Group 1], ReportGroup2 [Group 2] Group By ReportGroup1, ReportGroup2
A GroupByExpression is created with this string and added to the MasterTableView of the grid.
Then after the page loads, drag another column, such as LastName, to the group by panel. Now I have two GroupByExpressions.
Problem:
I first noticed the problem when I went to remove the LastName column from the group by panel. Everytime I would do this, it would always remove the first item in the group by panel, which was my original expression.
After taking a closer look, i noticed that the _createGroupPanelItems jscript function in the GridGroupPanel.js file is not creating the items with the correct HierarchicalIndex - which is then passed down in the postback as the index to remove from the group by panel.
As a temporary workaround, I have broken up the default expression to be two expressions, and it appears to be working as expected.
1 Answer, 1 is accepted
0
Accepted
Hi adam,
We fixed this and the fix will be included in our first service pack which will come after two weeks. Thank you once again for your report.
Regards,
Vlad
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We fixed this and the fix will be included in our first service pack which will come after two weeks. Thank you once again for your report.
Regards,
Vlad
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center