The QDSCV cannot bring such an item into view, since the item is not on the client. It is not here. It does not exist here on the client. The QDSCV does not know what is residing on the server. The item might not even exist the next time an OData request is sent. Someone might have deleted it for example. Or the server can be changing its data every millisecond as a matter of fact -- no one knows what is happening there on the server.
Think about it this way -- a request is made to the server and some data comes back as a result of this request. That is all the data that the collection knows about. It does not know what is going on on the other end in the meantime. Data might be changing every millisecond there. Unless something is brought back to the client -- it does not exist from the client's point of view. It can only work with the entities that are loaded in memory on the client.
I hope this makes sense.
So yes, you would have to devise some algorithm to do this "custom "item in page" calculation in the server" which goes beyond the scope of Telerik support.
All the best,
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>