Splitting attachment location
In 8.5 R09 (Onsite) we introduced a new table to support the possibility for splitting attachments in Service over multiple locations. Before introducing this table, the location of attachment was specified inconfig.attachment_path. In versions after 8.5 R09, this is no longer used, but replaced with attachment_location table. This table can contain 1 or more rows. The last row is considered by the application as “current” path. We also introduced a new field on the attachment table pointing to which row in attachment_location particular attachment is connected to.
This is a more complex procedure and we do not offer any GUI for this but must be performed in SQL by adding a new row into attachment_location. Since this row is added, all new attachments will be stored in the new location.
If you need to move attachments from one location to another this is even more complex as it would also require you to update the attachment table and so on. Do not recommend doing this without a consultant.
Update attachment location when moving Requests
If moving Requests and the attachment location has changed, you need to update the last row inattachment_location to point to the new path, for example: