Hi Lee Weisenberger,
Unfortunately at this point you cannot use fetch plans with web services. This is due to the fact that during serialization, when a property of the object is accessed, lazy loading is triggered and the value is retrieved.
This means even if you implement Fetch Plans, everything will be retrieved and sent. You can of course work around this problem, but it will take some effort. The solution here is to create custom DTO object that you can manually create and populate, and send them through the service. This object can contain only the fields that you require and that way you will send only the data that you require. You will also be able to implement Fetch Plans in this scenario due to the fact that the OpenAccess persistent objects will not be serialized, but the DTO objects instead. You can more info on the Fetch Plans find in these articles.
This way you will not trigger the lazy loading and send the correct data.
If you need further assistance do not hesitate to ask us.
All the best,
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.