In traditional versioning within an enterprise geodatabase, theDefaultversion often represents the published state of the database. Setting the Default version toprotectedensures that while all users can view it, only the geodatabase administrator or the version owner can edit it directly or post changes to it.
ArcGIS Pro
In the scenario provided, the editor follows these steps:
* Default Version Set to Protected:This restricts editing and posting privileges to the geodatabase administrator or the version owner.
* Creation of a Child Version from Default:The editor creates a new version branching from Default.
* Child Version Set to Protected:This means only the editor (as the owner) or the geodatabase administrator can edit this child version.
* Edits Saved to the Child Version:The editor makes and saves changes within this child version.
* Attempt to Reconcile and Post to Default:The editor successfully reconciles but encounters an error during the post operation.
The error during the post operation arises because, with the Default version set to protected, the editor lacks the necessary permissions to post changes directly to it. Only the geodatabase administrator or the owner of the Default version possesses the authority to perform this action.
ArcGIS Pro
Analysis of Options:
* Option A:Changing the access level of the child version from protected to public does not grant the editor the required permissions to post to the protected Default version.
* Option B:Requesting the owner of the Default version (typically the geodatabase administrator) to perform the reconcile and post is appropriate. This individual has the necessary permissions to post changes to the protected Default version.
* Option C:Creating a one-way replica and synchronizing is an unnecessary and complex approach for this situation.
Therefore, the editor shouldask the owner of Default to perform the reconcile and postto ensure the changes are integrated into the Default version.