Smartsheet files reach the shop, and the sync can't lose them

A drawing, markup or delivery ticket attached to a Smartsheet row now lands on the matching order in BuildingSwell, and a file added in BuildingSwell goes out to that row. Files sit where the row sits: on a flat sheet that is the order, and on a nested schedule a discipline row's files sit on that component or phase. Attachments on the sheet itself land on the sheet's project, or in the Documents Hub unattached when the sheet covers more than one project.

Re-uploading a corrected file under the same name is a normal day's work in the field, so it is treated as one: the file becomes a new version of the document that is already there, with the earlier version still in its history. Nothing is matched by filename.

The sync never deletes a file. When an attachment is removed in Smartsheet, its document leaves the active list and moves to the archive marked Removed from Smartsheet, with the time it was noticed, and you can restore it. Removing a file in BuildingSwell leaves Smartsheet alone, unless the file came from BuildingSwell in the first place and you have left removal propagation on.

Link attachments (Google Drive, Box, OneDrive, a plain URL) come across as references. The link is kept, the file is not copied, and opening it still needs whatever access the original does.

Off until you ask for it. Under Sync documents on the Smartsheet connection there is Pull files from Smartsheet and Push files to Smartsheet, plus switches for link attachments and for whether archiving here removes a BuildingSwell file from Smartsheet. The first run after turning pull on brings in the sheet's existing attachments; that runs as its own job in the background, so the usual sync keeps its normal pace while files catch up over one run or several. Its progress shows in the connection's Activity list, tagged Documents.