Hi King Wilder,
OQL is an interface to OpenAccess that has been there since the early days of the product, when there was no LINQ available. While it was a perfectly good solution at the time, we feel that is more or less inappropriate nowadays. These are the reasons to not include it, at least not publicly, in the designer. There is a way to use OQL in the new designer. What you need to do is extend the context class in a partial with a new property that exposes the inner scope. You code should look like this :
However we feel there is not need for this when we have Dynamic Linq
available. Also if you are comfortable working with OpenAccess Classic you can easily switch back to this. You just need to follow the steps described in this blog post
I hope this is helpful.
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