• Working With SmartSync
  • Publishing a Working Papers File
  • Creating a Synchronized Copy of a File
  • Connecting to a Parent File
  • Opening a Client File
  • Closing a Sync File
  • Abandoning Sync Copies
  • Returning SmartSync Files to a Non-Sync State
  • Replacing the Server Copy
  • Opening the Top-Level Parent File
  • Applying Changes to the Top-Level Parent File
  • Creating a Sync Copy for Another User
  • Managing Sync Copies
  • Creating a Synchronized Copy of Consolidated Files
  • Creating a Consolidation in a SmartSync Environment
  • Working Online
  • Working Offline
  • Sync Status
  • Synchronization Properties
  • Clear Synchronization Information Command
  • Publish to Server / Replace Server Copy
  • SmartSync and Lockdown
  • Consolidations With SmartSync
  • Working with Synchronized Consolidated Files
  • Templates and SmartSync
  • Locking documents for exclusive use

Publish to Server / Replace Server Copy

Creating and working with synchronized copies differs when using Cloud or a SmartSync Server. Among the differences are the Publish to Server and the Replace Server Copy commands.

Note: A progress bar with a Cancel button is displayed during both the Publish to Server and the Replace Server Copy operations.

Publish to Server

The Publish to Server command promotes a non-SmartSync Working Papers file on your local workstation to a SmartSync compatible file when used with Cloud or SmartSync Server. This function compresses the current file and creates a new _Sync folder to prepare for publication. The compressed file and its new _Sync folder are copied to the server and act as a top-level parent. The local file becomes a sync copy of the published file.

Other SmartSync users can connect to a published parent file and create sync copies.

Publishing a file requires:

• A non-SmartSync file in Working Papers with SmartSync.
• Cloud or SmartSync Server access.

Replace Server Copy

The Replace Server Copy command replaces the top-level parent copy on Cloud or the SmartSync Server with the current sync copy to act as the new top-level parent for its sync hierarchy. This function compresses a copy of the current file and creates a .spf file to upload to the server. A .spf file captures the current state of the synchronized copy to be promoted, enabling other synchronized users in the hierarchy to continue working. These files replace the current top-level parent files. The synchronized copy is retained on the local machine of the user and changes can be made while the compressed files are uploaded. Using this command will also result in a top-level parent file with all changes applied.

All other synchronized copies in the hierarchy do not need to re-connect to the new parent.