Distributed collaboration capabilities are offered as part of an early adopter program available to interested ArcGIS Online organizations. You must have an ArcGIS Enterprise 10.5.1 (or later) base deployment to participate in the early adopter program. For more information and to apply for the program, visit the Enterprise to Online Collaboration early adopter website.
Hosted or server-based feature layer items can be shared with the option to copy data. If you share a feature layer by copying data, a new item is created for collaboration participants, and the copied data is used to publish a feature layer for collaboration participants. The owner of the original feature layer can edit the feature layer and synchronize changes to the participants at a scheduled interval. To use this approach, the sync interval must be set in the collaboration workspace and sync must be enabled on shared hosted or federated feature layers.
If sync is not enabled when you share the feature layer with the sending organization's workspace, data is not copied. The feature layer created on the receiving organization references the data from the sending organization.
In such cases, the sending organization and administrator will receive a notification indicating that the item was shared as a reference rather than as a copy.
To share the feature layer as a copy, unshare it from the workspace, enable sync on the feature layer, and share it again.
Supported feature layer types for sharing as copies
The following types of feature layers support sharing data as copies:
- Hosted feature layers in ArcGIS Online.
- Hosted feature layers in ArcGIS Enterprise, where ArcGIS Enterprise meets the specifications of a base ArcGIS Enterprise deployment.
- Feature layers published to an ArcGIS Enterprise federated server where the data is stored in a registered enterprise
geodatabase. This type of layer is referred to as a federated feature layer. Create a federated feature layer using one of the following methods:
- Share a web feature layer that references registered data from ArcGIS Pro with one of your active portal's federated servers.
- Publish a map service with feature access enabled from ArcMap to a federated server.
You'll see the option to share feature layers as copies if all of the following are true:
- Collaboration participants are using ArcGIS Enterprise 10.6 or later and have access to Send or Send and Receive content.
- ArcGIS Enterprise participants must meet the specifications of a base ArcGIS Enterprise deployment.
- Feature layers are sync-enabled during the publishing process or once the service has been published.
- To enable sync for a feature layer published to a federated server, the data must be prepared appropriately in the enterprise geodatabase. See required data preparation steps for nonversioned and versioned data.
Properties of copied feature layers
When collaboration participants receive copied feature layers, the properties and behaviors described below apply.
Editing is disabled on feature layers received in a collaboration because synchronization is one way only; edits are only synchronized from the sending organization to participants. For this reason, it is recommended that you not enable editing on the layer in the participant organization or create editable views (if the participant is an ArcGIS Online organization) from these feature layers to support editing workflows in the participant organization. Edits made to the same feature in the host and participant organizations are overwritten in the layer in the participant organization during sync.
Enable editor tracking on feature layers before sending them to participating organizations. When the data is first copied to the receiving organizations, editor tracking values are reset. Editor tracking dates are set to the current timestamp in UTC, and creators and editors are set to the publishing user. Date, creator, and editor values are reset because this reflects when and who created the layer in the receiving organization. When syncing, the editor tracking dates from the sending organization are preserved. Therefore, from the time the data is shared, the layer in the receiving organization contains the dates that the edits were made in the sending organization. Creator and editor values for insert and update operations synced into the receiving organization are set to the publishing user from when the feature layer was copied.
It is possible for you to enable editor tracking on some feature layers in a sending organization and leave other feature layers without editor tracking enabled. How editor tracking is applied in the receiving organization depends on the type of feature layer you send and whether you send from ArcGIS Enterprise or ArcGIS Online as follows:
- When you send multiple hosted feature layers, and some have editor tracking enabled and some do not, all hosted feature layers created in the receiving organization will have editor tracking enabled. This is true when collaborating from ArcGIS Enterprise to ArcGIS Online.
- When collaborating from ArcGIS Online to ArcGIS Enterprise and editor tracking is enabled, all feature layers in ArcGIS Online and ArcGIS Enterprise will have editor tracking enabled.
If you enable editor tracking after adding the feature layer to the collaboration, the layers in the receiving organizations will not have editor tracking enabled.
If you unshare and share the layer to the sending organization's workspace, the layer will be recopied to the receiving organization workspaces with editor tracking enabled.
Access control settings are maintained for receiving organizations but have no consequence, since all features are owned by the publishing user in the receiving organizations.
When using collaborations to replicate items between ArcGIS Enterprise portals and ArcGIS Online, receiving organizations may want to enable delete protection on layers shared with them as copies. This is recommended to organizations that want to prevent layers from being deleted from the receiving organization if the sending organization leaves the collaboration or deletes the shared layers in the sending organization.
Once the receiving organization has enabled delete protection on a layer shared as a copy, sync will stop working if the sending organization turns off sharing on the layer. For example, if the sending organization turns off sharing on a shared layer item, and then edits the layer and shares the item with the receiving organization again, the edits will not be synced to the layer in the receiving organization. To reinstate sync on the layer, the receiving organization must first disable delete protection and delete the layer, and the sending organization must reshare the layer as a copy.
If you change the schema of a feature layer in either the sending or receiving organization, those changes are not applied when the workspace is synced. Examples of schema changes include adding or deleting fields, adding or deleting layers in a feature layer, and enabling or disabling attachments. The workspace sync operation includes only edits (insert, update, and delete operations) to layers or tables that were available at the time the feature layer was shared to the workspace. When there are schema differences, sync applies edits to the matching parts of the schema. For example, if a field is added in the sending organization, the new field is ignored when edits are applied during sync to the receiving organization's copy. To send schema changes to receiving organizations, unshare and share the layer to the sending organization's workspace.
When you copy feature layers that have time settings enabled, time is not enabled on the copied feature layer in receiving organizations.
If the feature layer's data in the sending organization is from a versioned enterprise geodatabase, edits made to the published version are sent when the workspace is synced.