Update a map service attribute configuration

patch

/fscmRestApi/resources/11.13.18.05/publicSectorSetupMapProfiles/{publicSectorSetupMapProfilesUniqID}/child/MapProfileReferences/{MapProfileReferencesUniqID}/child/MapServiceAttributes/{MapServiceAttributesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- AgencyId, MapProfileId and SystemMapProfileId ---for the Map Profile References resource and used to uniquely identify an instance of Map Profile References. The client should not generate the hash key value. Instead, the client should query on the Map Profile References collection resource with a filter on the primary key values in order to navigate to a specific instance of Map Profile References.

    For example: MapProfileReferences?q=AgencyId=<value1>;MapProfileId=<value2>;SystemMapProfileId=<value3>
  • This is the hash key of the attributes which make up the composite key--- AgencyId, MapProfileId, SystemMapProfileId and GisLayerName ---for the Map Service Attributes resource and used to uniquely identify an instance of Map Service Attributes. The client should not generate the hash key value. Instead, the client should query on the Map Service Attributes collection resource with a filter on the primary key values in order to navigate to a specific instance of Map Service Attributes.

    For example: MapServiceAttributes?q=AgencyId=<value1>;MapProfileId=<value2>;SystemMapProfileId=<value3>;GisLayerName=<value4>
  • This is the hash key of the attributes which make up the composite key--- AgencyId and MapProfileId ---for the Map Profiles resource and used to uniquely identify an instance of Map Profiles. The client should not generate the hash key value. Instead, the client should query on the Map Profiles collection resource with a filter on the primary key values in order to navigate to a specific instance of Map Profiles.

    For example: publicSectorSetupMapProfiles?q=AgencyId=<value1>;MapProfileId=<value2>
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
The following table describes the body parameters in the request for this task.
Root Schema : schema
Type: object
Show Source
  • Title: Enable Selection
    Maximum Length: 1
    Default Value: false
    Indicates whether the map layer is enabled for selection in the linked map page.
  • Title: Display Attributes
    Maximum Length: 400
    A collection of GIS object attributes to be displayed when the GIS object is selected.
  • Title: Unique Identifiers
    Maximum Length: 200
    A collection of unique identifiers for the GIS objects in the map layer.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorSetupMapProfiles-MapProfileReferences-MapServiceAttributes-item-response
Type: object
Show Source
Back to Top