nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Branch and Traditional versions in the same environment?

AbrahamDowner1

Our organization is researching branch versioning. Currently we are utilizing traditional versioning.

Can one user utilize a branch version that exists in an organization's Enterprise ArcGIS Portal environment and make edits to a feature class in ArcGIS Pro, while at the same time in the same organization have another user that has a traditional version for editing that is created in ArcCatalog and makes edits to the same feature class in ArcMap?

We are currently on version 10.6

Encuentra más publicaciones etiquetadas con

Accepted answers

George_Thompson

Branch versioned data and traditional versioned data can exist within the same Enterprise Geodatabase. The feature classes can be one or the other.

You cannot have ArcGIS Pro users edit branch versioned data and ArcMap users edit the same branch versioned data. Branch versioned data cannot be edited within ArcMap. (see limitations)

One option would be to create a web map / web app and allow the ArcMap users to edit the data via a browser.

Review this documentation: Enterprise data management strategies—Geodatabases | Documentation

Geodatabase‌

All comments

George_Thompson

Branch versioned data and traditional versioned data can exist within the same Enterprise Geodatabase. The feature classes can be one or the other.

You cannot have ArcGIS Pro users edit branch versioned data and ArcMap users edit the same branch versioned data. Branch versioned data cannot be edited within ArcMap. (see limitations)

One option would be to create a web map / web app and allow the ArcMap users to edit the data via a browser.

Review this documentation: Enterprise data management strategies—Geodatabases | Documentation

Geodatabase‌

AbrahamDowner1

Thank you for the response George. So, just to clarify, a user cannot create a version in ArcCatalog and then make edits to Feature Class A if there are edits that have already been made to Feature Class A in a branch version?

George_Thompson

Correct, a feature call can only be branch or traditional versioned. You cannot switch between them "on the fly" once versioned. Branch versioned data should not even load into ArcCatalog.

AbrahamDowner1

Thanks for clarifying that George. I did finally find it in the documentation here.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.