Word document is corrupt for unknown reason

Hi @Connor Shore I have alerted the open specifications team regarding your inquiry. A member of the team will be in touch soon. Regards, Obaid Farooqi - MSFT

Hi @Connor Shore I will investigate this for you and see if I can find the issue with your document. To help me look into this, can you please tell me: How was the .docm file created? How are you generating the .docx file (Word, Open Xml SDK, your own program, etc.)? Thanks, Michael Bowen Escalation Engineer - Microsoft Open Specifications

@Mike Bowen Hey Mike thanks for the help. Unfortunately I'm not sure how the .docm file was created as that was a customer of ours. I can ask our team to reach out to them but no guarantees on a reply. As for how it was created, it was generated using the Windward SDK. At a high level, the template contains "tags" which are field codes telling our engine to insert data from a database. After we parse the document, we insert the database info in place of the tags and then we rewrite it out to the desired output format, in this case a docx file. A good portion of the original ooxml is carried over but some new ooxml gets generated due to the new content within the document. Let me know if you have any more questions. Thanks!

@Mike Bowen Hey Mike thanks for the help. Unfortunately I'm not sure how the .docm file was created as that was a customer of ours. I can ask our team to reach out to them but no guarantees on a reply. As for how it was created, it was generated using the Windward SDK. At a high level, the customer creates a template in Word and puts in "tags" (which are field codes under the hood) that tell the engine to insert data from a database. Our engine parses the template, inserts the data from the database in place of the tags and the writes the output to the specified format (in this case docx). A good portion of the original ooxml gets carried over into output, however some new ooxml is generated due to the new content in the document from the tags. Let me know if you have any other questions. Thanks!. Also, sorry if this is a duplicate answer. I posted my reply as a comment but for some reason its not showing up on the ticket so posting this again just in case.

Hi @Connor Shore , I have found the issue with your .docm file. In CorruptOutput.docm the document.xml part has 30 tables. I'll use 1-30 to identify them. There are 3 issues are in table 26 and 1 issue table 29. In table 26, in the w:tr 4, in the last table cell (tc), w:tr 5 in the last table cell (tc), and w:tr 6 in the last table cell (tc), this w:r below is a child of w:hyperlink, but it should be a level higher and be a direct child of the w:p and sibling of the w:hyperlink.

<w:r>
	<w:fldChar w:fldCharType="end"/>
</w:r>

In addition, in table 29, in w:tr 2, in w:tc 2, the following element below is a child of w:hyperlink, but it should be a level higher and be a direct child of the w:p and a sibling of w:hyperlink.

<w:r>
	<w:rPr>
		<w:rFonts w:ascii="Century Gothic" w:hAnsi="Century Gothic"/>
		<w:b w:val="off"/>
		<w:color w:val="9E978E" w:themeColor="accent3"/>
		<w:sz w:val="20"/>
		<w:szCs w:val="20"/>
		<w:highlight w:val="yellow"/>
	</w:rPr>
	<w:fldChar w:fldCharType="end"/>
</w:r>

I've attached the repaired document.xml for the .docm file here: document-repaired.xml

The same errors appear in the document.xml part from CorruptOutput.docx, but repairing them does not make the .docx valid. I will continue to investigate this, but does the solution for the invalid .docm, give you any clue about what the issue could be with the .docx file?