Things to Remember

• Understand Connect Sync logic - Delete is allowed on Local machines. Delete is NOT allowed on server (except Local transfer).
• Set up a mock sync hierarchy and test it to expose convoluted / mixed Sync schedules). Test the sync behavior (Files, Folders) and decide if the workflow suits your needs.
• Use separate folders for each sync schedule. To avoid conflicts, assign a unique source and destination folder for each sync schedule. An example is shown in Image 01.
• If there have been significant folder changes on the server since your last sync, delete the synced folders on your local computer and sync again. This applies to both Bidirectional and Download syncs. Otherwise the folder hierarchy on the local machine may be corrupted.
• If you have files saved in External cloud storage, transfer them to your local machine first, and then sync them with Trimble Connect. Do not attempt to sync directly from the cloud.
• Managing multiple schedules on a single project

  If you set up multiple sync schedules for the same project (for example, one Bidirectional and one Upload-only), you must configure them to sync with completely separate, mutually exclusive folders on your local machine. For example, in Project1, if you want to set up Bidirectional and Upload only to sync simultaneously, use C:/users/<userID>/Folder1 and C:/users/<userID>/Folder2 on the local machine.

• Re-select folders if you change the local sync path. If you move the location of a synced folder on your computer, update Selective Sync to reflect the new path.

Image 01

Things to Avoid

• Avoid multiple schedules in subfolder hierarchy. Don’t have multiple sync schedules for the same project under the same folder hierarchy. This confuses the sync setup with the project data in the Connect server. For example:
  • [Bidirectional sync a folder C:/Users/<userID>/Folder A to server location Folder A (with selective sync of 5 items inside folder A) ] AND [Bidirectional sync a folder C:/Users/<userID>/Folder A to server location Folder A (with selective sync of some other 5 items inside folder A)].
  • [Bidirectional sync from folder C:/Users/<userID>/Folder A to server location Folder A] AND [Local transfer / Up Sync for same Folder A from C:/Users/<userID>/Folder A]
  • [bidirectional sync a folder C:/Users/<userID>/Folder A to server location Folder A] AND [bidirectional sync a folder C:/Users/<userID>/Folder A to server location Folder B]
• Avoid renaming or moving the folders on the Connect server after the first couple sync operations unless absolutely necessary. If Bidirectional sync has been set by multiple project members, it may upload the older content to the server.
• For Download-only and Upload-only sync directions, do not embed one project’s data into another project’s folder on the local machine. An example is shown here.