I have a client who has sent out a communication containing a link to a specific attachment version. Something like:
http://hostname:8080/download/attachments/31799912/TEST.pdf?version=2&modificationDate=1423603269604&api=v2
The problem that we have is that the attachment has now been updated, creating a new version and effectively breaking the link.
In dev, I have replicated this and tried to update the attachment data directly in the database, using the below:
update ATTACHMENTDATA
set DATA = (select DATA from ATTACHMENTDATA where ATTACHMENTID = <new version id>)
where ATTACHMENTID = <v2 id>
This seems to corrupt the file.
Any help would be great as I've hit a brick wall with this.
Is there a requirement to link the very specific version of the attachment?
A work around would be to link to the latest greatest version of the file, such as:
http://hostname:8080/download/attachments/31799912/TEST.pdf
Doing the above will always link you to the latest version of the file regardless if it has been updated, saved, or reverted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.