I'm reading about igGrid remote paging here : http://help.infragistics.com/NetAdvantage/jQuery/2013.1/CLR4.0?page=igGrid_Paging.html.
However, it's still unclear to me how I setup my remote paging if I'm NOT using the IG wrappers.
Could someone advise me on how to use recordCountKey and responseDataKey to configure this ? How do I implement my c# page method on the server-side, is it through the grid's "pageIndexChanging" event ?
As per the link above, it says :
"If you are implementing your own remote service (for example in ASP.NET or PHP), in order to properly initialize and render the pager, your service must specify both the responseDataKey (grid option) and the recordCountKey (paging option). The recordCountKey member tells the Paging widget how many records in total are in the backend. The responseDataKey specifies which property in the response contains the resulting data.
Therefore, when remote paging is used, the grid automatically generates the proper request parameters in the following way:
http:///grid/PagingGetData?page=2&pageSize=25"
ex/
$("#imGrid").igGrid({ //dataSource: jsonData,
dataSource: "/Margins/getTrades?level=account&entityName=" + entityName, responseDataKey: "Data.data", columns: [ { headerText: "Member", key: "entityName", dataType: "string", width: "100px" }, { headerText: "Margin", key: "Margin", dataType: "number", format: "double", width: "120px" }, ], features: [ name: "Paging", type: "remote", pageSize: 10,
recordCountKey: "Data.recordCountKey", }
});
and my controller code returns a nice-formatted Json object :
public dynamic getTrades(string entityName, string level = "member") { // Bind to Service (details omitted) BasicHttpBinding httpBinding = new BasicHttpBinding(); // Converts List type to Json format below JavaScriptSerializer ser = new JavaScriptSerializer(); var tradeData = myService.GetTrades(entityName); var jsonDataObj = Json(new { recordCountKey = 50, responseDataKey = "data", data = tradeData }); string jsonData = ser.Serialize(jsonDataObj); return jsonData; }
Hey Bob,
recordCountKey is a property you need to add to the response data which specifies the total number of records (so that the grid UI knows what to show and how to calculate, i.e. XXX of YYY records, where YYY is the total number of records). responseDataKey is a property holding your array of actual data records. As I see from your example above, those are already properly set. Do you need to add "Data" in front of ".data" and ".recordCountKey", respectively. Could you show me some example response JSON that you're sending to the browser?
As for the pageSize and page index ("page") parameters, you need to add extra parameters to your service method and read them in its implementation, so that you know which page the client requests. so you need to do something like this :
var tradeData = myService.GetTrades(entityName, pageSize, pageIndex); // where pageSize and page are parameters that the service will read from the URL, similar to entityName.
Then you need to modify your GetTrades method to take into account this pageSize and page (the index), in order to return the correct data portion.
Hope it helps. Thanks,
Angel
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 :
{"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,
yes this sounds perfect, and that's how I think you should do it as a best practice, assuming you aren't relying on our MVC wrappers. By the way, I think it is worth trying with the MVC wrappers, I am sure you will be surprised by how much work they do for you : ) I mean, paging, sorting, filtering, and you don't need to bind to a specific data source type - it's just IQueryable, so you can even pass a list of objects and all those operations I mentioned - paging/sorting/filtering/ etc. - will work out of the box, in any combination.
Let me know how it goes. Thanks,
Hey,
just checking if you need any additional help. Thanks
thank you kindly, Angel. At this point I will be discussing it with my team.
We had this idea where we would pull say 1k our of 10k records, then pull an additional 1k as needed. i.e. our concern was too many trips to the server if many users are clicking "Next" to page thru the grid..
Not sure how to implement it yet, but I suppose it's possible using the various igGrid events.
regards,
bob
Great, thanks. I suggest to try the remote paging first, and if you experience any performance issues, you may try alternatives. One alternative I can think of is to transfer all data to the client, and enable virtualization, so that your UI (the DOM elements) is virtualized. In this way the request may take longer, since you will be serving all data at once, but scrolling through records will be very fast and will happen entirely on the client side, so there won't be any additional server-side requests.
You can have a look at the following samples:
http://ko.infragistics.com/products/jquery/sample/grid/continuous-virtualization
http://ko.infragistics.com/products/jquery/sample/grid/virtualization
Thanks,
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
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.