Post

URL:: https://<root>/<serviceName>/VersionManagementServer/versions/<versionGuid>/post
Methods:: POST
Required Capability:: ArcGIS Advanced Editing user type extension license
Version Introduced:: 10.6

Description

The post operation allows the client to post the changes in their version to the default version. The reconcile operation must be performed before the post operation. The sessionId value performing the post operation must match the sessionId value used for the reconcile operation. To post a subset of edits in the current version to the default version, define the rows parameter.

The post operation is supported both synchronously and asynchronously.

Review the read and edit session requirements for version resource operations.

Request parameters

Parameter	Details
`f`	Specifies the output format of the response. The default response format is `html`. Values: `html` \| `json` \| `pjson`
`sessionId` (Required)	Specifies the client-generated session ID (GUID). Syntax : Use dark colors for code blocksCopy `1 sessionId = {3F2504E0-4F89-41D3-9A0C-0305E82C3301}`
`rows` (Optional)	Specifies the rows (features or objects) that will be used when posting a subset of edits in the current version to the default version. The object IDs provided must be edits in the current version, which can be obtained from the `differences` operation. When the `rows` parameter is used to post a subset of edits, the posted edits are no longer present in the version. All other features remain in the version. Another `reconcile` operation is required to see the posted features in the version. This parameter was introduced at ArcGIS Enterprise 10.9. The `rows` parameter only supports simple features, tables, and relationships. Additional support for utility network classes was introduced at ArcGIS Enterprise 11.3. Note For ArcGIS Enterprise 11.5 and later, it is recommended to use the partial post operation instead when posting a subset of edits. Syntax: Use dark colors for code blocksCopy `1 2 3 4 5 6 [ { "layerId" : <layerId>, "objectIds" : [ <objectId> ] } ]` Example: Use dark colors for code blocksCopy `1 2 3 4 5 6 7 8 9 10 [ { "layerId":0, "objectIds":[1207,1208] }, { "layerId":1, "objectIds":[809] } ]`
`async` (Optional)	Specifies whether the request will be processed asynchronously. If `true` , the request will be processed as an asynchronous job, and a URL will be returned that a client can visit to review the status of the job. The default is `false` . Values: `true \| false` This parameter was introduced at ArcGIS Enterprise 10.9.1.

JSON Response syntax

JSON response (when async = false):

Use dark colors for code blocksCopy
{
  "moment" : <datetime>,
  "success" : <true | false>,
  "error" : { // only if success is false
    "extendedCode" : <HRESULT>,
    "message" : <error message>,
    "details" : [ <detail> ]
  }
}

JSON response (when async = true):

Use dark colors for code blocksCopy
{
  "statusUrl" : <url>
}

JSON response to the status URL (when pending or in progress):

Use dark colors for code blocksCopy
{
  "status" : "<Pending | InProgress>",
  "submissionTime" : <datetime>,
  "lastUpdatedTime" : <datetime>
 }

Example usage

The following is a sample POST request for the post operation to post edits from a named version to the default version.

Request URL and parameters:

https://myserver.esri.com/server/rest/services/LandUse/VersionManagementServer/versions/24417758-0DBD-4EC3-95B0-467CAA47FC43/post

Use dark colors for code blocksCopy
f=json
sessionId={3E11BA55-9A50-4EDD-A694-D5C4F21CD40D}
async=false

JSON response:

Use dark colors for code blocksCopy
{
 "moment": 1602605793507,
 "success": true
}