Use branch versioned data

Use branch versioned data when you want to provide multiuser editing in a service-oriented architecture through feature services and your users don't need direct access to the geodatabase. To compare versioning types, see Versioning types in the ArcGIS Pro documentation.

To use branch versioning in your app:

Set up and share your data as described in the Set up and share versioned data section.
Bring your data into the app using the ServiceGeodatabase class, as described in the Work with branch versions section.

Branched versioned data can be edited offline the same way you edit feature services offline or use individual layers offline, as described in the Edit data from a branch version section.

Why use branch versioning

With branch versioning, editors can work within their own personal version of a geodatabase so that other users don't see incomplete work and editors don't block one another from accessing the data. Each version can represent ongoing work, such as a design or a group of work orders, work that can span multiple sessions and extend over a period of weeks or months if necessary.

Some common workflows for using branch versioned datasets include:

Multiuser editing, such as individual field crews working in their own branches
Modeling a variety of outcomes, with each scenario represented in its own branch
Editing and tracking different phases of a project

If you require multiple editors concurrently accessing services with the ability to work with their own set of edits, you must first register your data as branch versioned. When you share that dataset as a service, you have the option to enable the Version Management capability at the time of publishing, which allows for the creation and management of versions. For more information about setting up a database with branch versioning, see Register a dataset as branch versioned in the ArcGIS Pro documentation.

To edit branch versioned data, you must access it through a feature service. After registering data as branch versioned, publish the data to your organization's ArcGIS Enterprise portal as a web feature layer. Be sure you publish a layer that references registered data. The data will then be available as a feature service and you can edit it as part of your branch versioning workflows. For more information about how to share branch versioned data, see ArcGIS Pro help's Share branch versioned data.

Work with branch versions

The ServiceGeodatabase class represents a hosted geodatabase. You can create an instance of the class by providing the service URI and optionally the version name. You can also read the service geodatabase property from a service feature table.

A ServiceFeatureTable will have an associated ServiceGeodatabase if the feature table was loaded from a web map or if it was created from a service geodatabase (using ServiceGeodatabase::table()). A standalone service feature table, created using any of the constructors, will not have access to a service geodatabase.

Use ServiceGeodatabase::fetchVersions() to get information about the versions a service geodatabase contains that the current user has access to. The information includes the name, description, access level (private, protected, or public), creation date, and so on. You can create a new version by providing a name, description, and access level. You can access public and protected versions, and private versions you own. You cannot see information about, or connect to, private versions owned by other users.

The following steps show some common tasks when working with branch versions in a service geodatabase. These include getting the service geodatabase used by a feature layer, getting information about the current version, creating a new version, and switching the version used by the geodatabase to the new one.

Get the service feature table from a feature layer in the map.

Use dark colors for code blocksCopy
    // Get the feature table from a feature layer and cast it to a ServiceFeatureTable
    // (if the table is not a ServiceFeatureTable, it will be null).
    ServiceFeatureTable* table = dynamic_cast<ServiceFeatureTable*>(featureLayer->featureTable());

If the service feature table is not loaded, load it. Then get the service geodatabase from the table. If the service geodatabase exists but is not loaded, then load it.

Use dark colors for code blocksCopy
    // Continue if we have a service feature table.
    if (table)
    {
        // Get the service geodatabase from the service feature table.
        if (ServiceGeodatabase* serviceGdb = table->serviceGeodatabase(); serviceGdb)
        {
            // Continue if the service geodatabase's load status is not "Loaded".
            if (serviceGdb->loadStatus() != LoadStatus::Loaded)
            {
                // Load the service geodatabase.
                serviceGdb->load();
            }
        }
    }

Verify if the service geodatabase supports branch versioning. If it does, get a list of its versions and information about the current version.

Use dark colors for code blocksCopy
    // Continue if the service geodatabse support branch versioning.
    if (serviceGdb->isSupportsBranchVersioning())
    {
        // Call the service geodatabase's fetch version async method.
        serviceGdb->fetchVersionsAsync(this).then(this,[serviceGdb](const QList<ServiceVersionInfo*>& versions)

        {
            // Find the matching ServiceVersionInfo by name
            auto result = std::find_if(std::begin(versions), std::end(versions),
                [serviceGdb](ServiceVersionInfo* version)
            {
                return version->name() == serviceGdb->versionName();
            });

            // Continue if the result was found
            if (result != std::end(versions))
            {
                // Get the description from the result.
                const QString versionDescription = (*result)->description();

                qDebug() << versionDescription;
            }
        });
    }

Create service version parameters that define properties for a new version: a name, description, and access level.

Use dark colors for code blocksCopy
    // Create a new service version parameters.
    ServiceVersionParameters* versionParams = new ServiceVersionParameters(this);

    // Set the access, name and description properties on the service version parameters.

    versionParams->setAccess(VersionAccess::Private);
    versionParams->setName("DesignTwo");
    versionParams->setDescription("Experimenting with an alternate design");

Pass the parameters to the service geodatabase to create a new version. Then switch the current version of the database to the new one.

Use dark colors for code blocksCopy
    // Call the create version async method on the service geodatabase using
    // the supplied service version parameters.
    serviceGdb->createVersionAsync(versionParams).then(this,[serviceGdb, this]
        (ServiceVersionInfo* designTwoVersion)
    {
        // Call the switch version async method on the service geodatabase using the
        // supplied service version info's name.
        serviceGdb->switchVersionAsync(designTwoVersion->name()).then(this,[]()
        {
            // continue processing ...
        });
    });

Edit data from a branch version

Edits can be made to service feature tables from a branch version in the same way they are made to any ServiceFeatureTable. You can use the same process described in Edit data from a branch version for performing edits when working with a branch version. See Apply edits in a branch version for applying edits to the feature service and posting changes into the default branch. Similarly, navigate to Synchronize edits in a branch version for synchonizing edits to the feature service and posting changes into the default branch.

Use branch versioned data

Why use branch versioning

Set up and share versioned data

Work with branch versions

Edit data from a branch version