11 Answers, 1 is accepted
I can't reproduce this. Find attached my test project. Does it work at your side? What could be different in your case?
Greetings,Atanas Korchev
the Telerik team
Thanks for your prompt attention to our issue. I figure out that the issue is related to client-side(Ajax)-bound grids. I'm attaching your original project with the issue recreated and updated to use strongly-typed models. Basically, this works fine:
@{
//Server-side works fine. Client-side (Ajax-below) does NOT.
@(Html.Telerik().Grid(Model.Customers)
.Name("CustomerGrid")
.Columns(columns => columns.LoadSettings((IEnumerable<GridColumnSettings>)Model.Columns))
)
But this does NOT:
@{
@(Html.Telerik().Grid<dynamic>()
.Name("CustomerGrid")
.Columns(columns => columns.LoadSettings((IEnumerable<GridColumnSettings>)Model.Columns))
.DataBinding(dataBinding => dataBinding
.Ajax()
.Select("LoadCustomerData", "Home")
)
)
Thanks in advance for further looking this.
I was able to recreate the issue you have described. We have managed to address it and the fix will be included in the next internal build. Meanwhile I have attached a modified version of telerik.grid.js file which should fix the problem.
All the best,Rosen
the Telerik team
Thank you for your help. However, this did not fix our issue. If I use the new telerik.grid.min.js in the test project I provided, it does NOT have any affect. The hidden column still shows. If I use it with a later internal build, 2011.1.523, we're trying (to fix a popup-edit-close issue we're having as well) the hidden column does NOT get included in the HTML table at ALL. Ideally we want it included with a "display: none" css style so that we can grab the hidden-row/entity ID. Once again, thank you for your help.
I'm attaching the newest internal build. Please give it a try and let us know if it helps with the hidden columns issue.
All the best,Rosen
the Telerik team
I used the 2011.1.601 build you provided in the test project I posted previously and it actually made things worst. The grid data is not showing at all. Thanks for looking into this and further help would be greatly appreciated.
Please excuse us as there seems that is some other issue with the build I have sent you which cause the described behavior to appear. I have attached a newest build, please try it out, I hope it helps.
Regards,Rosen
the Telerik team
That seemed to have taken care of the issue. Thank you!
Question: Should we use this internal build in our app code or should we wait for the release? When is the next planned public release?
The internal builds are not meant to be used in production, therefore it is better to wait for the official release. The next official release is scheduled for mid July.
All the best,Rosen
the Telerik team
I'm afraid that I'm unable to recreate such behavior. Therefore, it will be appreciated if you could modify the previous sample as the issue to appear and send it back to us for further investigation.
Regards,Rosen
the Telerik team