Update parcel history

URL:
https://<root>/<serviceName>/ParcelFabricServer/updateParcelHistory
Methods:
POST
Required Capability:
ArcGIS Advanced Editing
Version Introduced:
10.8

Description

The updateParcelHistory operation sets the specified parcel features to current or historic using the specified record. When setting current parcels as historic, the Retired By Record field of the features is updated with the global ID of the specified record. When setting historic parcels as current, the Created By Record field of the features is updated with the global ID of the specified record.

Learn more about setting parcel history

Request parameters

ParameterDetails

gdbVersion

(Required)

Introduced at 10.8.

The name of the geodatabase version (the default is the DEFAULT version).

Syntax

1
gdbVersion=<version>

sessionId

(Required)

Introduced at 10.8.

The token (GUID) used to lock the version. If the calling client is editing a named version, the sessionId value is required. If the specified version is currently locked by another session, the request will fail if the sessionId value is not provided or does not match the sessionId value that holds the exclusive lock. If the client is editing the default version, the sessionId value is not required.

Syntax

1
sessionId=<guid>

parcelFeatures

(Required)

Introduced at 10.8.

The parcel features that will be set as historic or current. The features can be parcels, parcel polygons, parcel points, and parcel lines.

Syntax

1
parcelFeatures=[{"id":"<guid>","layerId":"<layerID>"},{...}]

setAsHistoric

(Required)

Introduced at 10.8.

Specifies whether the features will be set as historic (true) or current (false).

Syntax

1
setAsHistoric=<Boolean>

record

(Required)

Introduced at 10.8.

The unique identifier (GUID) of the record that will be assigned to the features set as current or historic.

Syntax

1
record=<guid>

async

(Optional)

Specifies whether the request will be processed as an asynchronous job and a URL that points to a location displaying the status of the job will be returned. See the topic regarding asynchronous usage for more information. The default is false .

Values: true | false

Syntax

1
async=true|false

f

Specifies the output format of the response. The default response format is html.

Values: html | json

Example usage

This example shows the steps for setting a parcel as historic using the updateParcelHistory operation.

  1. Start a service session on the version.

    Request URL and parameters:

    1
    2
    3
    https://machine.domain.com/webadaptor/rest/services/CountyFabric/VersionManagementServer/versions/E4DAED9D-C859-489B-9053-767A45F1D97C/startReading
    f=json
    sessionId={f24783f6-1e2a-47d6-9505-1b36898d632a}
  2. Start an edit session on the version.

    Request URL and parameters:

    1
    2
    3
    https://machine.domain.com/webadaptor/rest/services/CountyFabric/VersionManagementServer/versions/E4DAED9D-C859-489B-9053-767A45F1D97C/startEditing
    f=json
    sessionId={f24783f6-1e2a-47d6-9505-1b36898d632a}
  3. Set a parcel as historic using the specified record.

    Request URL and parameters:

    1
    2
    3
    4
    5
    6
    7
    8
    https://machine.domain.com/webadaptor/rest/services/CountyFabric/ParcelFabricServer/updateParcelHistory
    f=json
    gdbVersion=admin.Version1
    sessionId={f24783f6-1e2a-47d6-9505-1b36898d632a}
    parcelFeatures=[{"id":"{E60840C7-8A91-45BD-85C8-9DDF00BF2C82}","layerId":"13"}]
    setAsHistoric=true
    record={C379E2BB-7F9E-4593-B760-D4E908F8445D}
    async=false
  4. If edits are complete, stop the edit session.

  5. Stop and release the service session.

JSON Response syntax

The following response is returned when async is false:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
{
  "moment": <datetime>,
  "exceededTransferLimit: <true | false>,
  "serviceEdits": [  // only if transfer limit is not exceeded
    {
      "id": <layerID>,
      "editedFeatures": {
        "spatialReference": {<spatialreference>},
        "adds": [
          {
            "attributes": {},
            "geometry": {}
          }
        ]
      }
    },
    {
      "id": <layerID>,
      "editedFeatures": {
        "spatialReference": {<spatialreference>},
        "updates": [
          {
            "attributes": {},
            "geometry": {}
          }
        ]
      }
    }
  ],
  "success": <true | false>,
  "error": {  // only if success is false
    "extendedCode": <HRESULT>,
    "message": <error message>,
    "details": [<detail>]
  }
}

The following response is returned when async is true:

1
2
3
{
		"statusUrl": <url>
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.

You can no longer sign into this site. Go to your ArcGIS portal or the ArcGIS Location Platform dashboard to perform management tasks.

Your ArcGIS portal

Create, manage, and access API keys and OAuth 2.0 developer credentials, hosted layers, and data services.

Your ArcGIS Location Platform dashboard

Manage billing, monitor service usage, and access additional resources.

Learn more about these changes in the What's new in Esri Developers June 2024 blog post.

Close