Edit with branch versioning

Create, query, and edit a specific server version using a service geodatabase.

Use case

Workflows often progress in discrete stages, with each stage requiring the allocation of a different set of resources and business rules. Typically, each stage in the overall process represents a single unit of work, such as a work order or job. To manage these, you can create a separate, isolated version and modify it. Once this work is complete, you can integrate the changes into the default version.

How to use the sample

Once loaded, the map will zoom to the extent of the feature layer. The current version is indicated at the top of the map. Tap “Create” to open a dialog to specify the version information (name, description, and access). See the Additional information section for the restrictions on the version name.

Tap “Switch” to switch between the version you created and the default version. Edits will automatically be applied to your version when switching to the default version.

Select a feature to edit an attribute and/or tap a second time to relocate the feature.

How it works

1. Create and load a ServiceGeodatabase with a feature service URL that has enabled Version Management.
2. Get the ServiceFeatureTable from the service geodatabase.
3. Create a FeatureLayer from the service feature table.
4. Create ServiceVersionParameters with a unique name, VersionAccess, and description.

• Note - See the Additional information section for more restrictions on the version name.

5. Create a new version calling ServiceGeodatabase.makeVersion(parameters:) passing in the service version parameters.
6. Switch to the version you have just created using ServiceGeodatabase.switchToVersion(named:), passing in the version name obtained from ServiceVersionInfo returned from step above.
7. Select a Feature to edit its “typdamage” attribute and location.
8. Apply these edits to your version by calling ServiceGeodatabase.applyEdits().
9. Switch back and forth between your version and the default version to see how the two versions differ.

Relevant API

• FeatureLayer
• ServiceFeatureTable
• ServiceGeodatabase
• ServiceVersionInfo
• ServiceVersionParameters
• VersionAccess

About the data

The feature layer used in this sample is Damage to commercial buildings located in Naperville, Illinois.

Additional information

Credentials:

• Username: editor01
• Password: S7#i2LWmYH75

The name of the version must meet the following criteria:

1. Must not exceed 62 characters
2. Must not include: Period (.), Semicolon (;), Single quotation mark (’), Double quotation mark (”)
3. Must be unique

• Note - the version name will have the username and a period (.) prepended to it, e.g., “editor01.MyNewUniqueVersionName”.

Branch versioning access permission:

1. Public - Any portal user can view and edit the version.
2. Protected - Any portal user can view the version, but only the version owner, feature layer owner, and portal administrator can edit it.
3. Private - Only the version owner, feature layer owner, and portal administrator can view and edit the version.

Tags

branch versioning, edit, version control, version management server