I just identified the source of your problem, but I am pretty sure you will see this behavior (the control is disabled after client-side set_enabled(true) over its parent) for any control that is in this item template. This means that the datePicker should get this behavior too.
Anyway, this is happening because you try to enable the item from the client. I would like to suggest a solution:
- Enable the item server-side.
That way with only one line of code you are going to enable all of its child-controls.
If you do want to stick with the client-side - then you have to enable every control in the entire collection of child controls one-by-one (I would say that it doesn't worth it and it's a way better and cleaner solution to just set the item's Enabled property to true server-side). Also you will have to know the ID's of the elements which you want to enable. This should look like the following:
// This only works if the control in the template has js object representing it
"id of child control"
Hope this is going to help you!
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.