Contents
Who is allowed to view versioned data in ArcGIS?
Private: Only the owner or the geodatabase administrator may view the version and modify versioned data or the version itself. Protected: Any user may view the version, but only the owner or the geodatabase administrator may edit datasets in the version or the version itself.
How to reconcile and post versions in ArcGIS?
You can also reconcile and post versions using the Reconcile Versions geoprocessing tool and the Reconcile/Post button on the Versions tab when you are in the Versions view. You must be the only user currently editing the traditional version you are reconciling. No other user can be editing the target version.
How are version creation and permissions set in ArcGIS?
With the permissions set to Protected, any user can view the DEFAULT version, but only the geodatabase administrator can either edit DEFAULT directly or reconcile and post edits to it from other versions. To read an example scenario of creating versions and setting access on the versions, see Version creation and permissions example.
What happens when you make a change in ArcGIS Pro?
If there are conflicts, ArcGIS Pro initially resolves them in favor of either the version you are editing or the target version representation, depending on your preference. Once conflicts are initially resolved, you can review them one at a time and, if necessary, make any changes.
Limiting the number of versions is generally a good practice. It means you can conserve space on the server and reduce clutter for users. But, if your organization is required to save all versions for legal or other reasons, don’t apply any limits.
When to enable versioning in Microsoft SharePoint?
If you sort it, version 12 shows up in between version 1 and 2. It is a best practice to enable Versioning in a list at creation and not set a limit of major versions. It takes up very little space, and your end users will thank you for it.
When does versioning work in lists and libraries?
When a minor version of a file is created or updated in a library that tracks major and minor versions. When a list item or file is created or updated but not yet approved in a list or library in which content approval is required.