Intersoft Community - ClientBinding

JSON Serialization error, when grouping

Nikolay — Fri, 08 Apr 2011 04:03:27 GMT

Hello!

I have webgrid with about 18000 rows. There is column ProductId, the count of ProductIds is closed to this value (18000). When webgrid is grouping this data by the ProductId column. I see error from the webgrid "Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property." I tried to increase value of maxJsonLength in web.config. But it does not solve the problem. (In this case, the webgrid just hung.) Is there any solution, except just not group by ProductId?

Thank you!

Filtering data at WebGrid 7 with ClientBinding, Paging and ISLinqDatasource

somer@optima.com.tr — Fri, 23 Oct 2009 06:12:21 GMT

I have a webgrid with clientbinding and paging which is connected a ISLinqDataSource (Datasource is Entity Framework).

I would like to return filtered data, but i cant use "filter column" property because of the design and security issues (for example: user may unhide hidden column and clear filter, or i can't apply more than one filter for a single column like "code like 'a%' or code like 'b%' ").

And i cant use ISLinqDataSource's where property as WebGrid overrides it.

So i dediced to use FilteredColumns.AdvancedFilterExpression property.

It runs but has one important problem:

AdvancedFilterExpression is applied not while querying database, but applied after retrieving data by WebGrid. So if you set paging with 25 rows, you may see less than 25 rows in a pages, even may be all pages with no rows.

ClientBinding and Compression

danjransom@gmail.com — Wed, 19 Aug 2009 17:53:17 GMT

*I duplicated this post deliberately. The first post wouldn't open for me - error page.

I was looking at the client binding feature in the 2009 version of the grid to determine the bandwidth savings that this would produce for us. I found something very strange:

It loks like the client binding feature can increase the size of the data transmitted - rather than saving bandwidth. This is because the JSON data is sent uncompressed, while the older XML version of the data appears to be sent with with Gzip compression.

I tested this with the ClientBinding_BindingEvents.aspx sample page that comes with the grid. With server binding enabled, refreshing the grid on this page sends about 5.5 Kb (compressed down from 38.5 Kb) while client binding sends over 9 Kb.

Is there a way to turn on compression for the JSON data? I have II7 dynamic and static compression already enabled without effect.