Update one exception set

patch

/fscmRestApi/resources/11.13.18.05/exceptionSets/{ExceptionSetId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
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
Nested Schema : Exception Set Associations
Type: array
Title: Exception Set Associations
The list of exceptions that are included in the exception set.
Show Source
Nested Schema : Filters
Type: array
Title: Filters
Organizations, suppliers, item categories, and customers for which the exception set is applicable.
Show Source
Nested Schema : exceptionSets-ExceptionSetsAssociation-item-patch-request
Type: object
Show Source
Nested Schema : exceptionSets-Filters-item-patch-request
Type: object
Show Source
  • Type of filter. Values can be ORGANIZATION, SUPPLIER, CATEGORY, or CUSTOMER.
  • Value that uniquely identifies the filter based on its type. Depending on the FilterType, the value could be the organization ID, supplier ID, category ID, or customer ID.
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 : exceptionSets-item-response
Type: object
Show Source
Nested Schema : Exception Set Associations
Type: array
Title: Exception Set Associations
The list of exceptions that are included in the exception set.
Show Source
Nested Schema : Filters
Type: array
Title: Filters
Organizations, suppliers, item categories, and customers for which the exception set is applicable.
Show Source
Nested Schema : exceptionSets-ExceptionSetsAssociation-item-response
Type: object
Show Source
Nested Schema : exceptionSets-Filters-item-response
Type: object
Show Source
Back to Top