Select to view content in your preferred language

Branch Versioning Reconcile Error

128
1
11-27-2024 11:39 AM
compass_cartographic
Occasional Contributor

Newbie at Branch Versioning.  Enterprise 10.9, Pro 3.1.2

Connected to sde enterprise geodatabase and set the connection properties to branch.  On a feature layer, enabled branch versioning.  Shared as web layer.  Set Reference registered data with Feature checked.  Set location to a portal folder.  On configuration tab, checked option for Version Management.  Set instance to dedicated.  Published.  Brought branch versioned feature layer into Map in Pro.  Created a New Version.  Left Access Permission as Private.  Checked Change to this new version.

Edited to add a new point to non-default version.  

I can flip back and forth between the default version and the new version (test).  The default does not have the new point.  The new version does have the new point.  I can see the change (Insert 1) in the Version Changes panel.

Click Reconcile.  Following error message pops up "ERROR an edit operation is required".  Recreated the entire process a second time from scratch and get same message.  Cannot get past this error. Cannot find reference to it in any searches.

Any help greatly appreciated.  Thank you.

 

reconcile_error_branch_versioning_test.PNG

 

1 Reply
SaiKrosuri
Emerging Contributor

 

It looks like you're encountering an issue when trying to reconcile the branch version in your ArcGIS Enterprise environment. The error message "ERROR an edit operation is required" typically occurs when there are no changes or edits available to reconcile in the version you're working with. Here are a few steps and considerations to help you resolve the issue:

  • Ensure edits have been made and committed in the new version.
  • Check version configuration and make sure you’re reconciling the correct version.
  • Try creating a new version, making an edit, and attempting reconciliation.
  • Ensure there are no database locks or pending changes.
  • Test changing the version's access permissions to Public.
  • Review detailed logs for more insights into the error.

 

0 Kudos