Hi Amjad Shai,
We are facing an issue with one of our client having issues with Html to Excel conversion.
Please see the attachment for the html content.
while doing some research we found that after adding the code options.AutoFitColsAndRows = true;
solved the issues.
but in some previous issues you have suggested to remove this line of code for html content.
can you please check why we are facing issues with this html content.
we are using Aspose.Cells v21.6.0
current issue error message:
System.Exception: Column width must be between 0 and 255
at Aspose.Cells.Cells.SetColumnWidth(Int32 column, Double width)
at ?.?()
at ?.(String , ArrayList )
at ?.()
at ?.(Stream )
at ? .(String , Stream , LoadOptions )
HtmlPage11.zip (2.1 KB)
@kumar.penigalapati,
This issue is reproduced here and logged in our database for further investigation. You will be notified here once any update is ready for sharing.
This issue is logged as:
CELLSNET-48199 - Exception raised while loading HTML file without using "HtmlLoadOptions.AutoFitColsAndRows = true"
P.S. For better issue tracking this new thread is created, as previous thread was getting too long.
@kumar.penigalapati,
This is to inform you that we have fixed your issue now. We will soon provide you the fixed version after performing QA and incorporating other enhancements and fixes.
@kumar.penigalapati,
Please try our latest version/fix: Aspose.Cells for .NET v21.6.3 (attached)
Aspose.Cells21.6.3 For .Net2_AuthenticodeSigned.Zip (5.5 MB)
Aspose.Cells21.6.3 For .Net4.0.Zip (5.5 MB)
Aspose.Cells21.6.3 For .NetStandard20.Zip (5.5 MB)
Your issue should be fixed in it.
Let us know your feedback.
Hi Ashan Iqbal,
May I know what was fixed ? and what was the root cause of the issue ?
Thank you.
@kumar.penigalapati,
We are trying to collect more details about it and will share our feedback soon.
@kumar.penigalapati,
It was related to modifying setting column width exception under specific conditions when importing HTML file.
1 Like
The issues you have found earlier (filed as CELLSNET-48199) have been fixed in this update. This message was posted using Bugs notification tool by simon.zhao