I have a client who has sent out a communication containing a link to a specific attachment version. Something like:
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:
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:
Doing the above will always link you to the latest version of the file regardless if it has been updated, saved, or reverted.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs