To the Telerik Team: I waste a lot of time due to the fact
a) that remote datasources are handled differently depending on which widget you use (which from proper modular software design aspects is HELL)
b) that the documentation is far from beeing systematic.
For this particular Problem of a drop down list editor in a Grid my solution was (after wasting 4 hours finding it out):
1) do not use "type: odata" although I had a beautiful Odata Service for exactly the data required
2) prepare a separate json service that serves the data as a list, this because Kendo NEVER calls the data functions in the schema description to extract the data for the list properly.
This is not a professional API's behaviour! Please, Telerik Team: Clean up the datasource code and provide homgeneous usage of the datasource in EVERY widget. By being consistent, you can systematically document the api and once someone has understood the (though important) datasource concept, he or she does not need to read through inumberable examples and stackoverflow posts get it to work. And really: if I build a OData Web Service Infrastructure, there is no sense in serving the same data on a second address via simple JSON. Or do I miss a point here???