Incoming documents not recognised as versions

Original post by Stephanie Jones: stephanie.jones@morton-fraser.com

We have had a number of reports from out users that amended documents being returned to us as email attachments are not being recognised as versions. So, we have saved v1 to a matter and have sent it to the other side who have amended it and returned it. However when the user tries to save the attachment as version 2 (and we are doing this by actually opening the document and selecting Save As), they are being prompted to select a client matter then being forced to save the attachment as a new document. 

This is intermittent. The latest incident of this, the other side has returned 3 of our documents in one email. Two of them are not recognised as versions, but the third is and is therefore not prompting for a client matter, immediately launching the save wizard and prompting to save as a new major version (as per our settings). Has anyone else experienced this? It means our users are having to save the attachment to our network and use the Import as Version option from the matter document.

Original post by Jamie Francis: jamie.francis@emwllp.com

Yes, this has happened to our users as well. We have always had to put it down to 3rd parties stripping the document metadata - either on purpose or inadvertently with software - but it's very hard to know if this is what's happening

Note that using "Save As" will always prompt for client/matter because it tries to save as a new document.

Original post by Stephanie Jones: stephanie.jones@morton-fraser.com

Thanks Jamie, metadata stripping had been our original thought, but we have since confirmed with one of the senders anyway that they are not using any kind of metadata stripper.

We have our Default Versioning Option on Save As set to New Major Version in the Admin Kit, so we get prompted to save as a new major version when we click Save As, assuming the document already exists on the matter, with the exception of these few anomalies, that is.