iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
I first must apologize that I am new to Linq and to handling large amounts of rows.
Here is my problem:
I have a WebGrid (Ver 7) that is bound to a ISLinqDatasource. The datasource has approx. 10,000 rows.
The grid runs fine and is fast. But, it appears that the gouping and export only look at the fist page of data. I have set the export to AllData but it still only exports the current page.
The grid has a column called Catgeory that has vaules from 20 to 72, but when i drag the column into the GroupBy header, it only returns the fist 2 categories (20 and 21).
I am a bit baffled, I have tried playing with the data and caching settings but have not been able to get it working.
I have attached the web page showing my settings.
I am using Visual Studio 2008 with .net 3.5 and SQL Server 2003 all running in 64bit mode.
Pleas help...
I have found that here is a workaround for this issue.
if you have PagingExportMode="ExportAllData" and Classic Paging enabled, you can get around this bug by setting the Paging Size For Virtual Load to something greater than the maximum rows in your grid.
So, if you have 12000 rows in your grid and want to export all, make sure the Paging Size For Virtual Load is set to something greater than 12000.
For some reason, even though you are using Classic Paging the Paging Size For Virtual Load is controlling the Export Capabilities.
Steve...
It seems the PagingExportMode="ExportAllData" will not work for self reference grid. I have submitted a bug report for further analysis. We will inform you if there is any update or progress regarding this issue.
Regarding the grouping feature, this is the default behavior. The paging will also take account the grouped row. If the grouped row from a category already reach a page size, the curernt page view will only show a category. The WebGrid already have a property PagingDetectPartialGroupRows under LayoutSettings for you to show some information if the group data could not hold all row in the current page view.
Is there an answer to this problem?
Our client does not want to have to export every page seperately.
If this is not going to be fixed, we will have to abandon using your grid.
We will be forced to go back to DevExpress as our grid control simply because although their grid is not as robust as yours, everything works.
Please let us know ASAP, our client is waiting for an answer from us.
Very dissapointing.
Regarding the PagingExportMode issue in self reference grid, the issue is currently still open.
Our developer is currently focusing on the WebUI Studio 2010 R1 release, so the self reference grid export issue fix is currently being planned for May release.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname
Creating your account...