English

FAQ: What are some best practices to ensure a successful synchronization of offline edits in Collector for ArcGIS?

Question

What are some best practices to ensure a successful synchronization of offline edits in Collector for ArcGIS?

Answer

When attempting to synchronize offline edits in Collector for ArcGIS, synchronization may fail due to several issues. These issues include but are not limited to an unstable connection to the Internet, dataset sizes, or irregular synchronization schedules. The following are some useful tips to ensure a successful synchronization of offline edits in Collector for ArcGIS.

  • Synchronize collected data frequently

    It is advisable to synchronize collected data frequently as large volumes of accumulated data can be time consuming to complete during the synchronization process. Large datasets require longer durations to synchronize, and this increases the possibility of time-outs and errors to occur. For more information, refer to Collector for ArcGIS: Prepare maps for offline use.

  • Synchronize over a stable Internet connection

    Collected data, in large volumes, require a longer duration to fully synchronize. A stable Internet connection reduces the possibility of being disconnected during the synchronization process with the server. In the event that a synchronization fails due to an unstable Internet connection, the collected data may be corrupted or damaged.

  • Test the synchronization with smaller datasets before synchronizing larger datasets

    In the event that the collected data size is large, to determine if the Internet connection to the server is stable, users can first synchronize a smaller set of data before synchronizing the larger sets of collected data. Reducing file or attachment sizes through the properties of the items to be synchronized can help reduce the overall size of the collected data.

  • Ensure no edits are made to parent datasets after replication

    Once the replica has been downloaded to the devices, avoid making changes to the parent webmap as each replica contains a JSON that matches the webmap. Changes to the original webmap causes a mismatch.

Note:
If changes are made to the original dataset, delete all copies of the replicas, and download the new dataset again.

Related Information