Update a single configuration

patch

/fscmRestApi/resources/11.13.18.05/incentiveCompensationSummarizedTableConfigurations/{incentiveCompensationSummarizedTableConfigurationsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Incentive Compensation Summarized Table Configurations resource and used to uniquely identify an instance of Incentive Compensation Summarized Table Configurations. The client should not generate the hash key value. Instead, the client should query on the Incentive Compensation Summarized Table Configurations collection resource in order to navigate to a specific instance of Incentive Compensation Summarized Table Configurations to get the hash key.
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 ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 30
    The aggregation function to be used on the specified measure.
  • Maximum Length: 30
    The attribute column to be included in the configuration.
  • Maximum Length: 30
    The data type of the attribute column to be included in the configuration.
  • Maximum Length: 30
    The source object from which the attribute is being retrieved for summarization.
  • Maximum Length: 30
    The type of the record to be included in the summarized table. This will determine if the attribute is included as a dimension or a measure.
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 : incentiveCompensationSummarizedTableConfigurations-item-response
Type: object
Show Source
Back to Top