Prevent Overwriting Title & Slug When Importing DOCX into an Existing Article
under review
sneha sree
Hi team,
Raising this feedback on behalf of Panaya.
When importing a .docx file into an existing empty article, the system automatically overwrites the article title and slug based on the file name. This happens even when the user has manually set the title and slug earlier.
Customer's workflow and concern:
The user creates an empty article with a specific title and slug.
They often share this slug/URL with their R&D team for integration on the Panaya application.
After a few weeks, they import content from a Word file into the same article.
The DOCX import unexpectedly overwrites the article title and slug.
This breaks previously shared URLs and causes confusion
Customer expectation:
If the title and slug were manually defined, the import should not overwrite them, or the user should be prompted before changes.
Log In
D
D360 Product Management
marked this post as
under review
Mohamed Shakheen
Hi Plum Bass
Thank you for detailing your workflow and the issue you’re encountering - this context is very helpful.
You’re absolutely right in your observation. Today, when a DOCX file is imported into an existing (empty) article, the system automatically derives the article title and slug from the file name and overwrites any previously defined values. This behavior is currently system-driven and does not differentiate between manually set metadata and auto-generated ones.
We understand how this impacts your workflow, especially when the article URL is shared early with your R&D team for integration purposes. Overwriting the title and slug post-import can break existing links and introduce unnecessary confusion, which is not ideal for production or pre-production environments.
From an expectation standpoint, your ask is completely valid:
If the title and slug are already manually defined, they should either be preserved during import, or
The system should clearly prompt the user before making any changes to these fields.
We agree this is a usability gap and have taken this feedback back to our product team for evaluation. We are currently assessing possible improvements to make the import behavior more predictable and user-controlled, while ensuring backward compatibility with existing workflows.
Thank you again for flagging this. Feedback like this directly helps us improve the product experience, and we’ll keep you posted as we make
sneha sree
Raised on behalf of Plum Bass