Pending Review
Last Updated: 31 Jul 2016 19:31 by jose antonio
Created by: jose antonio
Comments: 1
Category: ClientDataSource
Type: Feature Request
This is needed, in case of controlleed server error, need to notify the user with the message that comes in the body of the request, and currently there is no way to get it.

Refers to ticket: 1031709

Pending Review
Last Updated: 02 Feb 2016 09:46 by Doug
Created by: Doug
Comments: 0
Category: ClientDataSource
Type: Feature Request
It would be nice to have a very quick and easy way to create a datasource, at one end just put in the SQL or point it to EF at the other end JSON WebAPI. 
It needs to work well with AngularJS.
It would be nice if you also have a look at BreezeJS to see have you can traverse data keys(more an Entity Framework thing). Even if consistent T4 data frameworks are created.
What this means to me is that I can web service enable existing SQL and how have to worry about security, that the endpoints can be monitored or scaled up. So I can move quickly from Proof of Concept to Hardened Product with out the usual friction.
Pending Review
Last Updated: 15 Jun 2015 20:42 by Robin
The RadClientDataSource is a wonderful control to greatly simplify binding controls to data for client side operations. 

I'm finding though that I don't have many scenario's where I can get the data in one swoop. An example is an event log viewer with 100000 logs that I don't want to transfer to the client in one transfer. Rather, with a custom date range that can be set via date pickers, I'd like to be able to tell the data source to go back and get fresh data for the new filter parameters. 

Other scenario's can be for contributions where in our app, people are part of teams and they can be part of multiple teams. Upon switching contexts, from one team to another, the data needs to be refreshed because there's many thousands of records so I cannot load everything at once on the first go, besides, that kills the network pipeline.

I guess what I'm getting at is that I find there is the need to have the ability to filter the data by passing parameters from controls on the client to filter data returned from a stored procedure expecting said parameters. It's really the only way to go when you have screens that are generic that deal with large datasets because any alternative will kill performance.