Welcome to the ASP.NET Core feedback portal. We’re happy you’re here! If you have feedback on how to improve the ASP.NET Core, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

We are currently considering Syncfusion as rich text editor for the enterprise web application.
The application is receiving SFDT string from UI and converts it to DOCX for further processing.
After testing I noticed that there are some scenarios when resulting DOCX file is corrupted.

All components both UI and Backend have the latest version as on 7/20/2023.

Steps to reproduce:

1. Copy content from file Source file to copy from.docx (file is attached) into Javascript DocumentEditor control Control(or open file using 'open' button) 

2. Get the SFDT string from UI component

3. Convert to DOCX using Syncfusion.EJ2.WordEditor.AspNet.Core (ver 22.1.39)        

var document = WordDocument.Save(sfdtString);        
using var memoryStream = new MemoryStream();        
document.Save(memoryStream, Syncfusion.DocIO.FormatType.Docx);        
var byteArray = memoryStream.ToArray();
System.IO.File.WriteAllBytes(@"Converted.docx", byteArray);

4. Check the structure of result DOCX file using Open XML SDK
5. Observe the error:

Description: The attribute 'http://schemas.openxmlformats.org/wordprocessingml/2006/main:val' has invalid value '0'. The Enumeration constraint failed.
ErrorType: Schema
Node: DocumentFormat.OpenXml.Wordprocessing.BiDiVisual
Path: /w:document[1]/w:body[1]/w:tbl[1]/w:tblPr[1]/w:bidiVisual[1]
Part: /word/document.xml

Also if export to DOCX from UI using 'download' button, 
almost always
the the result DOCX files have structural issues
 
as well. It can be verified by downloading the document from demo page and checking it with