Skip To Content

Share branch versioned data

Editing branch versioned data is only available through feature services. After registering data as branch versioned, you will need to publish the data to your organization's portal as a web feature layer. The data will then be available as a feature service and can edited and participate in branch versioning workflows.

For more information on feature services, see What is a feature service?

For more information on sharing web feature layers, see Web feature layer.

When you publish branch versioned data, there is an option to enable Version Management capabilities. The version management service is responsible for exposing the management capabilities necessary to support feature services that work with branch versioned datasets. To work with branch versioned data in isolated versions and have it participate in versioning workflows, Version Management must be enabled when publishing the service.

Share As Web Layer pane

The following features are enabled for the feature layer when published with the Version Management capability checked:

  • Access to the Versioning contextual tab and version manager view (Versions tab). This allows you to do the following:

  • Undo and redo capabilities (when working in a named branch version other than default). This allows you to do the following:

    • Undo or redo individual edits that have been made throughout an edit session.
    • Save or discard edits for the entire edit session (when working within a named version).

Analyzers are used to validate branch versioned datasets when publishing as feature layers. The following conditions are enforced via these analyzers:

  • 10.5 and earlier ArcGIS Server instances are not supported.
  • If Version Management is enabled under Capabilities, all datasets must be of the same registration type.
  • If Version Management is not enabled under Capabilities, publishing a mix of data types is allowed with the exception of traditional versioning.
  • All data must belong to a branch workspace.
  • All data must be published from the default version.
  • The connected geodatabase user must be the owner of the data.
  • If the feature layer is going to participate in a utility network, the following must also be true:
    • Definition queries must not be present.
    • All fields must be visible.

These errors will show up when you run the analyzer or try to publish in the Share As Web Layer pane. All analyzer errors must be resolved before you can complete the publishing process.

Share branch versioned data

  1. To share branch versioned data as a web feature layer, do one of the following:
    • Share the map and all of its layers as a web layer. On the Share tab in the Share As group, click Web Layer Web layer.
    • Share selected layers from the map as a web layer. Select the layers in the Contents pane. Right-click and choose Sharing > Share As Web Layer Web layer.
  2. Provide the name for the web layer. By default, the web layer will be saved to My Content. You can save the web layer to a folder in My Content by typing the folder name or browsing to an existing folder.
  3. For Data, check Reference registered data. Enabling Reference registered data will include a map image layer.
  4. For Layer Type, click Feature.
  5. Complete the Item Description fields for Summary and Tags.
  6. Specify how the web layer will be shared:
    • My Content—This option only references content in your personal workspace named My Content. Your content is inaccessible to other users.
    • My Organization—This option allows your content to be shared with all authenticated users in the organization.
    • Everyone—This option makes your content public. This means anyone can access and see it.
    • Groups—You can share your content with groups you belong to and members of those groups.
  7. Optionally, you can enable version management on the branch versioned dataset. This is not required when sharing branch versioned datasets, but it is required if you would like the feature layer to participate in version workflows as described previously in this topic. Click the Configuration tab and under Capabilities, click Version Management.
  8. Optionally click the Content tab to view the new web layer or layers and all associated components.

    Since Reference registered data was selected, you can click the Federated Servers drop-down arrow to choose where the layer will be shared. Only federated servers that you have access to will be listed.

  9. Click Analyze to check for any errors or issues. You must resolve all errors. If any issues are discovered, they show on the Messages tab. Right-click each message to get more information, read the help for the error or warning, and access suggested fixes.
  10. Once validated, click Publish to share your web layer.
  11. Once the web layer has successfully published, click the Manage the web layer link to manage the web feature layer through your portal. Since Reference registered data was selected earlier, the link will take you to the map image layer.