We have a web app project with a React front-end and a .net 5 API. I believe the issue here is coming from the actual conversion of the .doc in the back end, but if there's a more appropriate solution relating to React I am not opposed to moving/cross-posting this query there instead.
I've been searching through the forums for similar examples to this issue and the closest was some content omission, here:
We have some customers who have old letter templates that appear to be created in previous versions of Word that cause some issues when converted to .sfdt. I have sanitized the content of and attached the best example I could find.
Some old images, or maybe it's just related to their formatting settings, and table or column layouts appear to be causing issues. The first document is the original and the 'After Save' document is what it appears as in the web page and how it saves when exported as a .docx.
I don't understand xml that well but if I convert the first document to a docx and view it in an xml viewer it looks like the image is within an mc:AlternateContent tag. It makes sense that it wouldn't be supported but I'm wondering if there's anything I can do to enable these images to convert more successfully.
If there is anything, like a compatibility mode or something to enable pictures that would allow for the background picture and three column layout in the first page of the document. The margins on the second page also appear to have been cut a bit, but I'm less concerned with that aspect, although if there's any additional information you could provide regarding the conversion process, it would be great to get a better understanding of which documents may cause issues.
We are checking the document provided by you and will update the details by January 10, 2023.
Thank you for the response. I was just wondering if there was any update regarding this issue with the doc converter.
If you're still looking into it I understand - just curious if there's any additional info at this time.
Matt, Sorry for the inconvenience.
We need additional time to check the document provided by you and will update the details by January 13, 2023.
Matt, on further analyzing the attached input Word document, we found that the corresponding element is "Group shape." Currently, the document editor doesn’t provide support for group shapes. We've already logged the feature request for this and don’t have any immediate plans to implement this feature. So, we recommend you ungroup the group shape images in the DOC file and try it as a workaround. We have attached a modified (ungrouped shapes) DOC file for your reference.
You can check the status of this feature at the following link: