Update a relationship

patch

/fscmRestApi/resources/11.13.18.05/crossReferenceRelationships/{crossReferenceRelationshipsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- ItemRelationshipId, InventoryItemId and ApplicableOrganizationId ---for the Cross-Reference Relationships resource and used to uniquely identify an instance of Cross-Reference Relationships. The client should not generate the hash key value. Instead, the client should query on the Cross-Reference Relationships collection resource with a filter on the primary key values in order to navigate to a specific instance of Cross-Reference Relationships.

    For example: crossReferenceRelationships?q=ItemRelationshipId=<value1>;InventoryItemId=<value2>;ApplicableOrganizationId=<value3>
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 : DFF
Type: array
Show Source
Nested Schema : Translatable Attributes
Type: array
Title: Translatable Attributes
The Translatable Attributes resource manages the translatable attributes for item relationships.
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : crossReferenceRelationships-translatableAttributes-item-patch-request
Type: object
Show Source
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 : crossReferenceRelationships-item-response
Type: object
Show Source
Nested Schema : DFF
Type: array
Show Source
Nested Schema : Translatable Attributes
Type: array
Title: Translatable Attributes
The Translatable Attributes resource manages the translatable attributes for item relationships.
Show Source
Nested Schema : crossReferenceRelationships-DFF-item-response
Type: object
Show Source
Nested Schema : crossReferenceRelationships-translatableAttributes-item-response
Type: object
Show Source
Back to Top