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
Hi,
There appears to be a big bug in the Export functions (use any, client, server and any type). Using the webUI samples for 2009 R1 SP1 run the sample "ProgrammaticExportServerSide", select the "Export Grid" button in the Grid tray, select Excel and view the Excel listing. Now take TEXT and export. Compare the 2 outputs and they are not the same! Excel has extra records with only an address field with all other columns blank. Then look at the Text notice that some records have portion of the text that belongs to other columns in the record above. I have attached 2 samples, Excel and Text of the Northwind export. You can run the Client Side script on the ProgrammaticExportClientSide, running it first for Excel and then Text and notice the same problems.
As an example: Here is the Excell export
VINET Vins et alcools Chevalier Paul Henriot Accounting Manager 59 rue de l'Abbaye Reims 51100 France 26.47.15.10 26.47.15.11
Here is the Text export:
VINET,Vins et alcools ,Paul Henriot,Accounting Manager,59 rue de l'Abbaye,Reims, ,51100,France,26.47.15.10,26.47.15.11
You can change the file extension of the text file to csv and open it in Excel and then compare the 2 sheets and there are big differences.
Anything more on this? This is still happening with the SP1 Refresh.
The text file issue occurs because there is a , character in the Address column while we are using , as a column separator. In order to remedy this issue you could enclosed the Address data in a " " during Export server side event in order to set the data as a single column data. Here is the snippet:
protected void WebGrid1_Export(object sender, ISNet.WebUI.WebGrid.ExportEventArgs e){ foreach (WebGridRow wgRow in e.Table.Rows) { wgRow.Cells.GetNamedItem("Address").Value = "\"" + wgRow.Cells.GetNamedItem("Address").Value + "\""; wgRow.Cells.GetNamedItem("Address").Text = "\"" + wgRow.Cells.GetNamedItem("Address").Text + "\""; } }
Hi Glenn,
Ok that takes care of the problem with the Address filed, but now run the Sample called "Exporting". First don't touch anything and export to text. Look at Product ID 59 and notice that the end of the Product Name "ult" is on a seperate line. Now apply your code to it (note I am using the VB samples) to Product Name and run the page and export. Notice 59 is correct now but Product ID 34 and 70 are messed up. There are no comma's in this data. Now apply the above code to the only other string field "QuantityPerUnit", re run and export, and see other fields are messed up. This appears to only occur with Text. What other data maybe causing this?
In my Data, it appers to be Dates that are causing the problem.
More information.
1. The text export seems to mess up if there are more than 50-60 records, possible overflow problem?
2. If you convert a column to a TemplatedColumn, the problems I am experiencing withthe ExporttGrid show up. I have modified your sample if you want to see it, but all you need to do is create a TemplateColumn and then in the InitializeRow event modify the template text.
I'll send a sample if you need one.
This is my last hope, if I can't get export to run then looks like I need to find a replacement.
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