Hi Angel,

Yes in fact I do need to qualify responseDataKey with "Data.data". The reason is when the following controller code returns jsonData,

           var tradeData = myService.GetTrades(entityName);          
            var jsonDataObj = Json(new
            {
                recordCountKey = tradeData.Count(),
                responseDataKey = "data",
                data = tradeData
            });
            string jsonData = ser.Serialize(jsonDataObj);     

            return jsonData;

jsonData is then returned back to the client with the property "Data" as the top level of jsonData. Take a look at my debug screen shot :

and here's a record sample of the jsonData return value (getTrades() c# method): you'll see "Data" then "data" .

{"ContentEncoding":null,
"ContentType":null,
"Data":{
"recordCountKey":37,
"responseDataKey":"data",
"data":[
{"ExtensionData":{},"Account":"0012F","BuySell":0,"FaceValue":0,"Member":"3D","SettlementDate":"\/Date(1421298000000)\/","TradeDate":"\/Date(1358226000000)\/","TradeID":null,"contractID":"CGZU12","qty":3,"source":"IX"},
{"ExtensionData":{},"Account":"0012F","BuySell":0,"FaceValue":0,"Member":"3D","SettlementDate":"\/Date(1421384400000)\/","TradeDate":"\/Date(1358312400000)\/","TradeID":null,"contractID":"CGZZ12","qty":13,"source":"IX"},
{"ExtensionData":{},"Account":"0012F","BuySell":0,"FaceValue":0,"Member":"3D","SettlementDate":"\/Date(1421470800000)\/","TradeDate":"\/Date(1358398800000)\/","TradeID":null,"contractID":"CGZH13","qty":1,"source":"IX"},
{"ExtensionData":{},"Account":"0012F","BuySell":0,"FaceValue":0,"Member":"3D","SettlementDate":"\/Date(1421557200000)\/","TradeDate":"\/Date(1358485200000)\/","TradeID":null,"contractID":"CGZM13","qty":69,"source":"IX"}
}

Hey Bob,

ok great, in that case if you apply my suggestion to pass the paging (pageSize & page) parameters to your service and propagate them to the GetTrades method, remote paging should work. Not sure what GetTrades does (I mean how it connects to your backend) so if you need more details please let me know.

thanks

Angel

Hi,

myService.GetTrades() is just a backend service just returns to me an iEnumerable list of trade records, which I then serialize into jsonDataObj.

My controller is also called getTrades(), which I call directly from the dataSource property of igGrid.

Where I'd like clarification is the on dataSource of the igGrid :

       dataSource:  "/Margins/getTrades?level=account&entityName=" + entityName

My understanding is that your grid automatically appends the appropriate pageIndex and pageSize params as per this IG link :

 http://help.infragistics.com/NetAdvantage/jQuery/2013.1/CLR4.0?page=igGrid_Paging.html

"In the case of the “remote” scenario, for every page change, the grid initiates a request to the dataSource specified in the grid, by automatically calculating and appending all necessary parameters to the request, such as pageIndex and pageSize."

So do I NOT need to add any params to the dataSource call ? But I do need to add the pageIndex and pageSize parameters to my controller first, correct ?

For now, I could just write the custom code here in getTrades controller, then eventually discuss it with the backend service coders.

ex/

        public dynamic getTrades(string entityName, string level = "member", int pageIndex, int pageSize)
        {
             // service binding...           
            JavaScriptSerializer ser = new JavaScriptSerializer();

            var tradeData = iRAService.GetTrades(entityName);

            var jsonDataObj = Json(new
            {
                recordCountKey = tradeData.Count(),
                responseDataKey = "data",
                data = tradeData
            });
            string jsonData = ser.Serialize(jsonDataObj);     

            return jsonData;            
        }

hey Bob,

that's right, you don't need to add any params to the dataSource url, the grid will do that automatically before it sends out the request. The only thing you need to change is make your service accept pageSize and page, and then either:

1) Filter the IEnumerable that you get from the backend yourself, based on those page index and pageSize or

2) pass those to the backend call, and ask your backend service developes to take them into account - i strongly recommend this, mainly  for performance reasons

Thanks

Angel

Right, I agree it's best for the backend service to accomplish this for performance. In the meantime, however, I'll work up a beta version before discussing it further. I'd like to get a handle on it first.

And the other thing that concerns me has to do with sorting. So if the user decides to sort on say "trade Data" column, and my service always returns data by the Trade Id for example, is that something I need to account for in my logic ?

thanks.

Bob

We are following the same above steps to use remote paging in Ig tree grid. below are our codesnippet, we are getting error like arrays and iterates are only allowed when we give URl in dataSource. Please help us on this.

<ig-tree-grid [options]='gridOptions' [widgetId]='id'></ig-tree-grid>

this.gridOptions = {
responseDataKey: "Data.Records",
dataSource: "/api/DealsList?UserID=" + this.userID,
height: "500",
width: "100%",
columns: [
----------
],
features: [
{
name: "Paging",
type: "remote",
pageSize: 20,
recordCountKey: "Data.recordCountKey",
pageIndexUrlKey: "pageIndex",
pageSizeUrlKey: "pageSize"
}
]
};

Json I'm getting from API:

{"ContentEncoding":null,
"ContentType":null,
"Data":{
"Records":"[{\"DealId\":47r3254545456,\"Phase\":541,\"DealName\":\"StatusChangeTest\",\"StatusId\":22457,\"StatusName\":\"Re-Authorization Approval Pending\"}]",
"recordCountKey":3634,
"responseDataKey":"Records"},
"JsonRequestBehavior":0,
"MaxJsonLength":null,
"RecursionLimit":null}

error while i'm running :

ERROR Error: Error trying to diff '/api/DealsList?UserID=X202942'. Only arrays and iterables are allowed

ERROR CONTEXT [object Object]

Do we missing some thing on this setting for remote paging.

Hi Alexander.

I would like to know about if with remote paging can I still using this kind of filters on the grid.

Currently, before team developer than mine,  were sending all data to the client and doing paging, sorting and filtering all sucessfully but when end workdays at office, IIS (Internet Information) died because there were so much clients connected and getting around 3 thousands register in this way.

I am planning change for remote paging, but I am wondering about these filters since they are so useful for our users.

Thanks in advance. Here in the company we got IG licensed btw.

Great to hear, thanks Bob.

Angel

Thanks Angel. And yes, we've been already playing with virtualization - and we like it very much.

We just have to be careful that eventually the returned dataset doesn't get into the 10s of thousands...

thank you.

Bob