Maximum page size 1000

[abdul1224]

I am using the provided odata code for XAMDataGrid and having some below queries.
-Maximum 'PageSizeRequested' accepting is 999 if I am trying to give more than that I am getting an error, how can we increase the page size?
-suppose we are having 1000 records and page size requested is 100, in this case, first page data binded and other pages data is received on scrolling or moving bottom, can we get all the pages data in the background one by one if we keep the page ideal also?
-Getting an error on filtering the data in the provided sample.

Thanks in advance.

[brianlagunas]

Our best guess is that it could be a limitation of the odata client we use. The server can limit the page size also. 1000 is way too large a page size, I'd wager. You want the pages to be able to download quickly so that they can seamlessly stream in and parse in the background. You don't want to hit any CPU spikes when it parses a page.

Can you provide more information about the feed and settings you are using in the sample?

[abdul1224]

1. So is there any possibility to set page size more than 1000? what do you mean by the limitation of the OData client are you referring to 'Simple.OData.Client.Net40'? If yes then when I am updating it to the latest version(5.0) it's not working unable to get data from API(client).

2. suppose we are having 1000 records and page size set is 100, in this case, first page data binded on load and other pages data is received on scrolling or moving bottom, but can we get all the pages data in the background one by one if we keep the page ideal also without scrolling?

3. Getting an error on filtering the data in the provided sample provided.
   

4. Is there a possibility to add parameters to URI? as we have ODATA API with some custome parameters.

[gmurray81]

1. could you elaborate on your rationale for setting the page size so high? Its not something I'd recommend, as it could make the time to decode an individual page long enough to impact responsiveness, and most server solutions will refuse to honor a page size request of that magnitude without artificially tweaking a bunch of settings.

2. the actual data source will predict and load records ahead of your scrolling, but I can't recall if the WPF version of the grid supports telling the data source its current position as to enable this behavior or not. If this does not appear to be the case, that would be a feature request. I don't recommend setting the page size so high to try to work around this, if that is the case.

3. this seems like a mismatch between versions. I think you may be using an incompatible version of NetAdvantage vs this open source repo. A breaking change was enacted at some point to change the type to IOperationFilterExpression from OperationFilterExpression. You may need to either adjust the verison of the repo, or the version of the product.

4. This is recommended via extending this open source repo to add parameters to the client, which is why these data source implementations are open source, in fact, to limit the amount of customizability we need to build into them up front. If there is sufficient interest in a particular piece of functionality, we'll add it to the repo when time permits, or based on a feature request.