topic Re: Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel in Web AppBuilder Custom Widgets Questions

Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel

deleted-user-YYhuCJuuEn9L — Fri, 09 Jan 2015 20:01:52 GMT

FYI, in the Developer version of the WAB, I noticed that when exporting the Attribute Table to CSV in IE11, Excel didn't seem to be recognizing the comma delimiters and rows would show up in a single column. I tried a workaround found in this thread on stackoverflow:

javascript - execCommand in internet explorer saves the csv file using USC-2 Little endian encoding, how to save it with…

And made the following edit to the widgets/AttributeTable/Widget.js file:

And the CSV now displays as expected in Excel (2010). Hope this helps.

Update: This issue seems to not have been fixed in the 1.1 version. The workaround I used in the 1.1 version is this:

Re: Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel

RobertScheitlin__GISP — Fri, 09 Jan 2015 20:31:12 GMT

Ryan,

Be sure to call tech support and report this bug.

Re: Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel

JeremiahGlascock1 — Thu, 29 Jan 2015 22:24:45 GMT

All,

There is also a bug with the export to CSV. If you have commas in the data, it will offset the columns. For example: Field Name: Fullname

Value: "Doe, John"

Re: Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel

RobertScheitlin__GISP — Fri, 30 Jan 2015 00:10:25 GMT

Jeremiah,

Are you using the WAB 1.x version or a beta version? I just tested in WAB 1.0 and a column with a comma in it exported just fine.

Re: Export Attribute Table to CSV in IE11 - Not Formatted Properly in Excel

JeremiahGlascock1 — Fri, 30 Jan 2015 13:42:14 GMT

Robert,

The problem persists in the WAB within Portal. It looks like the code in the developer WAB and what is in the WAB built in Portal for ArcGIS are different. This is not the only time i have seen this. I am going to try to copy the code from developer WAB to the server for the attribute widget and see what resultI get. I am guessing it will work. I wonder how many other places the code is different. I presume there are two differentdeveloper teams at ESRI working on these products and are not aligning themselves.

Thanks