As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
Hi, I've been evaluating Nuxeo for the past days, and I was surprised to learn about the explorer integration via webdav/windows sharepoint services. However when editing a pre-existing document the associated meta-data and versioning information is destroyed. In my particular use-case I was editing the document with Microsoft Office 2013, I was wondering if this is a common issue and if there are some configuration steps that could be taken to retain the information. Ideally, the document should be incremented with a minor version on every change, as opposed to being treated it's a new document all together.
Edited to provide detailed reproduction steps:
Video:
Software versions:
What you describe as "ideally" is what should happen. Please edit this question to have detailed reproduction steps, including the exact version of Nuxeo used.
Added detailed instructions for reproduction including all relevant version numbers I could find p.s. nuxeo is installed under Windows Server 2012.
Thanks for the video.
As you can see in the Nuxeo URL, when Microsoft Word saves the file, it saves it under the name 996D933E.tmp instead of saving it with the original name. Nuxeo has no way of knowing that this is a new version of the old file and just update it as a new version with an incremented number.
996D933E.tmp
To fix this we would need to understand how Microsoft Word does its saves through WebDAV and try to work around the fact that it loses some context and see if we have a way of reacquiring the correct info.
I opened NXP-16335 but this is not scheduled at the moment.
If you have a WireShark trace of the whole exchange it could help debugging.
Sorry, I don't have a Wireshark trace, I could provide one on request though, but I think this problem is reproducible via standard means.
Yes sure but the environment you describe is not one I have immediately available, so the WireShark trace would speed up debugging for us.