This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 83%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
When PowerPoint exports to ODF format (file extension .odp), then it writes draw:id attributes without associated xml:id attribute. That is invalid, see https://docs.oasis-open.org/office/OpenDocument/v1.4/cs01/schemas/OpenDocument-v1.4-schema.rng You can see in the schema in rng:define name="common-draw-id-attlist", that it is not allowed to have the draw:id alone.
Notice that the draw:id attribute is already deprecated in ODF 1.3. PowerPoint should not write it at all, but write xml:id instead. But if it needs to write it for backward compatibility with older versions of PowerPoint, then it must be written together with an xml:id attribute and both must have the same value. Find more about the draw:id attribute in section 19.187.3 in part 3 of ODF standard. https://docs.oasis-open.org/office/OpenDocument/v1.4/cs01/part3-schema/OpenDocument-v1.4-cs01-part3-schema.html#__RefHeading__1417084_253892949
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 23%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESN%3C/text%3E%3C/svg%3E)
Hello Regina,
Thank you for your question about Microsoft Open Specifications. One of the team members from Office Specifications will review the details and assist you further.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 69%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHV%3C/text%3E%3C/svg%3E)
Welcome you to Microsoft Q&A forum.
Thank you for your detailed and feedback regarding the issue with PowerPoint's ODF (.odp) export functionality. We sincerely appreciate you taking the time to provide specific details, including references to the official OpenDocument v1.4 standard
The current implementation, which writes the draw:id attribute without a corresponding xml:id, results in a non-compliant file. We understand the importance of adhering to open standards to ensure interoperability.
You may consider the following workarounds:
1.Manual XML Edit (Quick Fix for Small Files):
odp files are ZIP archives. Extract the contents (e.g., using 7-Zip or unzip command).
Open content.xml in a text editor or XML editor (like Notepad++ or VS Code with XML plugins).
Search for elements with draw:id (<draw:frame draw:id="somevalue">).
Add xml:id with the same value: <draw:frame xml:id="somevalue" draw:id="somevalue">.
Save, re-zip the folder (ensure the structure matches the original), and rename to .odp.
Test validation using an online ODF validator or by opening in LibreOffice.
2.Remove Deprecated Attributes (If Not Needed for Compatibility):
If backward compatibility isn't a concern, you could script removal of draw:id entirely, relying solely on xml:id for IDs.
Since this is a user concern about a feature, encourage you to submit your feedback directly to Microsoft. You can do so through the Microsoft 365 Feedback Portal. User feedback plays a significant role in future feature development. We highly recommend submitting your feedback directly through the Microsoft 365 Feedback Portal. User feedback is a key driver in shaping future updates and enhancements. By sharing your experience, you could help the Microsoft product team better understand user needs and improve the overall experience for everyone.
As a forum moderator, I’m here to help guide discussions and share information based on Microsoft documentation and community knowledge, but I don’t have access to internal product insights or the ability to give the precise answer from a developer perspective.
If you have any additional concern, feel free to comment below. I be more than happy to assist.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you for your quick response. I have repeated the report in the feedback portal.
A comment to manually fixing the file: It is not necessary to unpack the file. Unpacking makes things unnecessarily complicated. A packer like 7-Zip, for example, allows to change the content of included files without unpacking. That has the advantage, that you need not worry about the structure. The mimetype file remains the first entry and remains uncompressed, as specified by the ODF standard.