UC 2022: Branch Versioning (resources)

[#1]

This is reserved for helpful resources for the 2022 user conference sessions on branch versioning: 

Core documentation –

• Branch version scenarios
• REST API – Version Management Service

Blogs –

• To Branch or Not to Branch – An Introduction to branch versioning
• Branch Versioning: Setting the Stage
• Editing and Administration with Branch Versioning – It’s Showtime!
• Version administrator for branch versioned data
• New Manage Tab on Properties Page

Sessions - UC 2022 branch versioning presentations

• Enterprise Geodatabase: Branch Versioning (Technical workshop)
• Enterprise Geodatabase: Demonstrating Branch Versioning Workflows (Demo theater)

Documents included: 

• Presentation slides in PDF for both sessions
• Summary questions and answers from both sessions

[RadhakrishnanNeelakantan]

@MelissaJarman Do we have a Technical whitepaper on Branch Versioning ala Traditional Versioning?

[MelissaJarman]

@RadhakrishnanNeelakantan - We do not yet have a technical whitepaper for branch versioning. Most of our content has been in the form of blogs and core reference documentation. Please share what type of information you are looking for specifically in the whitepaper. 

[RadhakrishnanNeelakantan]

@MelissaJarman  Thanks for your response. We have been looking into details of System tables pertaining to branch versioning and Utility Network, to get deep understanding of the structure for future manipulations.

The earlier whitepapers on versioning , Geodatabase etc. gave us clear idea of the System tables being used , details and significance of system table columns. This sort of information would help us to do deeper technical work with branch versioning and Utility network.

[SU00861536]

@MelissaJarman @myesri  Hi, i want to publish a geoprocessing service using python to change the branch version to default version. I tested the same code on python its working but when published the geoprocessing service version is not changing into default version. can you share some idea...

[RobertKrisher]

@SU00861536  can you provide more context to why you want to do this? The tool you described (https://pro.arcgis.com/en/pro-app/2.9/tool-reference/data-management/changeversion.htm) only updates the version on the layer within the context of the script that is currently running. So if you have a larger process that you want to have run in a particular version you may need to have a larger geoprocessing service for performing all the work using either this + other tools or you could consider using the ArcGIS API for Python. I discuss the considerations for these approaches and which API to use in an Utility Network Integration Strategies  blog, although the considerations for versioning apply to any branch version dataset / service.

[SU00861536]

We are using BRANCH versioned feature service to perform editing's in ArcGIS Pro 3.0.

After completing the edits, requirement is to change the added feature service in TOC from 'child version' to 'SDE.DEFAULT' version using arcpy

Python code we are trying to use:

import arcpy

aprx = arcpy.mp.ArcGISProject(r"C:\abc_Pro\Project\abc_Aprx.aprx")

m = aprx.listMaps('Map')[0]

for lyr in m.listLayers():
if (lyr.name == "APPROVED"):
       arcpy.management.ChangeVersion(lyr, "BRANCH", "sde.DEFAULT", None, "INCLUDE")
       print(lyr.name)

When we run the above script in "Python Notebook" in ArcGIS Pro, it is working fine.

When we run the same from python script (ex: abc.py), script executing with out errors but services are not changing to "DEFAULT" version.

Anything we are missing in this. Appreciate help on this. Thanks.

[RobertKrisher]

Ah, it makes sense that it would work in a python notebook and not a geoprocessing service, and here's why. A geoprocessing service runs remotely on the server, which means it can't make any modifications to the current ArcGIS Pro user's project / map / layers.

If all you need is a tool to change the "approved" layer to default you could create a small python toolbox with a single tool to do that and place it on a network share for your users to access.

You may also be able to rewrite your tool so it does all the work in a geoprocessing service without needing to update the users map, or you could make the entire process available via a python toolbox on a network share (or copied locally, or in the users project).

You can read more about how geoprocessing services on this page in the online help.

You can read more about python toolboxes on this page in the online help.