Free Support Forum - aspose.com

HTML to DOCX throws exception when table contains cells more than 63 using C#

Hello,

Is the issue for the limitation of html table having more than 63 cell been fixed?

We are inserting attached html using builder.InsertHtml(updatedBlobText), however while saving the aspose word document , exception gets rasied of row having more than 63 cells.

Could you please help in providing a solution to this issue. I have attached the input html and code snippet 63Cells Issue.zip (2.7 KB)

Thanks,

@sweta107

We have not found any issue while inserting the shared HTML into document using DocumentBuilder.InsertHtml method.

Please create a standalone console application ( source code without compilation errors ) that helps us to reproduce your problem on our end and attach it here for testing. We will investigate the issue and provide you more information on it.

@tahir.manzoor,

I am attaching the source code snippet for your reference, it contains the Inputhtml embedded. Error does not occur while DocumentBuilder.InsertHtml method, it occurs on document.save

ConsoleApp1.zip (9.7 MB)

Waiting for your response

Thanks,

@sweta107

We have logged this problem in our issue tracking system as WORDSNET-20085 . You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Can you please provide an ETA for this issue

@sweta107

Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. We work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

You reported this issue in free support forum and it will be treated with normal priority. To speed up the progress of issue’s resolution, we suggest you please check our paid support policies from following link.
Paid Support Policies

The issues you have found earlier (filed as WORDSNET-20085) have been fixed in this Aspose.Words for .NET 20.9 update and this Aspose.Words for Java 20.9 update.