topic Using Branch Versioning in AGOL in Geodatabase Questions

Using Branch Versioning in AGOL

glasbergenm — Fri, 30 Sep 2022 07:01:14 GMT

Based on the advise of our Enterprise Geodatabase administrator, I looked at using branch versioning my data on our Enterprise Geodatabase to be able to keep the original data 'clean' (the DEFAULT version) and allowing a client to make changes in a predefined version. This way, I'm able to reconcile the changes before posting them to the default version. Testing this behavior shows that this works fine when using the data in ArcGIS Pro. But we use these services in eg. web maps, web map applications and storymaps either through a PDS, ArcGIS Online or an Enterprise environment. Every change I make through these portals immediately appears in the default version and I can't figure out how to change this.

Re: Using Branch Versioning in AGOL

ChristopherCounsell — Fri, 30 Sep 2022 08:01:51 GMT

This is expected behaviour. When branched versioning first came out, only ArcGIS Pro supported the version management capability and other apps (Web Map) would apply the edits directly to default.

Over time apps such as the Experience Builder have introduced some support for branched versioning:

https://www.esri.com/arcgis-blog/products/arcgis-enterprise/data-management/manage-your-branch-versions-with-arcgis-experience-builder/

https://doc.arcgis.com/en/experience-builder/latest/configure-widgets/branch-version-management-widget.htm

General scenarios:

https://pro.arcgis.com/en/pro-app/2.8/help/data/geodatabases/overview/branch-version-scenarios.htm

For offline maps:

https://enterprise.arcgis.com/en/server/latest/publish-services/windows/offline-maps-and-branch-versioned-data.htm#ESRI_SECTION1_C30D73392D964D51A8B606128A8A6E8F

Please don't forget the kudos 🙂

Re: Using Branch Versioning in AGOL

glasbergenm — Fri, 30 Sep 2022 10:42:18 GMT

Hmm, that explains why that part doesn't work. It does not explain why the Experience Builder widget doesn't recognize the dataset as versioned (where Pro does recognize it). But perhaps this could be the result of the ArcGIS Server version on our Enterprise environment?

Re: Using Branch Versioning in AGOL

MarlonAmaya — Fri, 30 Sep 2022 19:00:17 GMT

@glasbergenm

The above article are great resources. Here is another post from a user as well with a good resource.

https://community.esri.com/t5/arcgis-enterprise-questions/use-branch-version-in-map-viewer/m-p/1146143#M32475

Re: Using Branch Versioning in AGOL

glasbergenm — Mon, 03 Oct 2022 08:13:33 GMT

Thnx. The solution using https://serverName.esri.com/server/rest/services/serviceName/FeatureServer/4?gdbversion=versionName seemed very straightforward, but didn't work either. Annoying thing is that Enterprise Builder doesn't recognize the feature layer as versioned, if I add the data it returns Not a valid versioned service (although it works perfectly fine in ArcGIS Pro).

Re: Using Branch Versioning in AGOL

Jchapman_COE — Fri, 07 Mar 2025 23:09:34 GMT

I know it's been a while, but did you ever manage to find success with the Branch Versioning widget in Experience Builder? I'm not seeing much online about the "Not a valid versioned service" error and we're having the same problem.