I need to build a fairly robust grid and if I do it without paging then my updates that call a Web 2,0 API cause memory issues and cause the browser to crash. If I use a 12 record page then even updating 5000 values from the api is not a problem. However. Since one of the fields is build by concatenating a couple of other fields and adding some font colors to certain words if I try to export the grid to Excel without paging all of the record first it throws errors. If I take out all of the html code and use just a straight text from the api then the export is fine
the code that I use is just simple html JavaScript code:
pubInformation: function(field, data, column) {
res += "<font color='#FF6600'>Affiliations: </font>"
if (data["Affiliation"] !== null ) {
data["Affiliation"] = data["Affiliation"].replace( Organization,"<font color='#3366FF'>" + Organization + " </font>" )
data["Affiliation"] = data["Affiliation"].replace("&","and" )
if (department !== null){
department = department.trim()
data["Affiliation"] = data["Affiliation"].replace(department,"<font color='#3366FF'>" + department + " </font>" )
if( department.includes("&")){
department = department.replace("&", "and")
data["Affiliation"] = data["Affiliation"].replace(department,"<font color='#3366FF'>" + department+" </font>" )
}
}
if (email !==null){
data["Affiliation"] = data["Affiliation"].replace(data["Email"],"<font color='#3366FF'>" + data["Email"] +" </font>" )
} res += data["Affiliation"]
The error is an Excel error when trying to open the file saying: We found a problem with some content.... would you like us to try ...
Without changing one line of code but only changing my page view size to 200 and paging through each page and then exporting again- then the export is fine.
Is there a work around for this? I can't ask my end users to be sure to page through all 5000 records before they export.
