Cannot edit branch versioned data

[DeanMoiler]

I've recently upgrade a system from 11.1 to 11.3 and have noticed that branch versioned editing via ExB / version manager is no longer possible.

"Error: You cannot edit as you have not been assigned required user type extensions: [Advanced Editing]"

At 11.1 this branch version workflow did not require an additional license and worked with a creator UT, but now an additional license extension for previously licensed capabilities is required. 

Are there any other solutions other than purchasing additional licenses, or doing away with branch versioning?

[AlisonWieckowicz]

We experienced the same.   We didn't find an alternative.   

[ToddW_stl]

Do you have access to any of these licenses?

"For all branch versioning workflows with ArcGIS Enterprise 11.2 or later, users can alternatively use licenses of ArcGIS Indoors, Roads & Highways, or Pipeline Referencing in lieu of the Advanced Editing user type extension." from this blog post

[DeanMoiler · Accepted solution]

Sorry @ToddW_stl I didn't catch your response until now, but yes that blog post was very helpful thank you!

I do see that yesterday (2025-09-24) Esri have released a patch which lists this as a bug 

• BUG-000178298 - Allow editing on simple branch versioned datasets without the ArcGIS Advanced Editing user type extension license.

ArcGIS Server Branch Versioning Licensing Patch

Other than this patch an additional license was listed as needing for this in the current functionality matrix

But happy that it's no longer an issue for simple branch versioning. They do mention in the patch blurb this does not yet allow access for the Web Editor application, and only for the service endpoints themselves, so does work fine for ExB / WebMap editing.

I've applied the patch and can confirm that we can now once again edit branch versioned data with a standard CreatorUT and not needing Advanced Editing extension.

[LarryYoung]

Hi All,

Just put out a blog related to the licensing change and the patch highlighted in Dean's response above.  The blog can be found here:  Licensing Update for Branch Versioning 

Hopefully it helps.

larry