Update a fee schedule map

patch

/fscmRestApi/resources/11.13.18.05/publicSectorFeeSchedules/{publicSectorFeeSchedulesUniqID}/child/FeeLine/{FeeLineUniqID}/child/FeeScheduleMapD/{FeeScheduleMapDUniqID}

Request

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

    For example: FeeLine?q=AgencyId=<value1>;FeeScheduleId=<value2>;EffectiveStartDate=<value3>;EffectiveEndDate=<value4>;FeeScheduleLine=<value5>
  • This is the hash key of the attributes which make up the composite key--- AgencyId, EffectiveEndDate, EffectiveStartDate, FeeScheduleId, FeeScheduleLine, FieldNum and MappingType ---for the Fee Schedule Map Data resource and used to uniquely identify an instance of Fee Schedule Map Data. The client should not generate the hash key value. Instead, the client should query on the Fee Schedule Map Data collection resource with a filter on the primary key values in order to navigate to a specific instance of Fee Schedule Map Data.

    For example: FeeScheduleMapD?q=AgencyId=<value1>;EffectiveEndDate=<value2>;EffectiveStartDate=<value3>;FeeScheduleId=<value4>;FeeScheduleLine=<value5>;FieldNum=<value6>;MappingType=<value7>
  • This is the hash key of the attributes which make up the composite key--- AgencyId, FeeScheduleId, EffectiveStartDate and EffectiveEndDate ---for the Fee Schedules resource and used to uniquely identify an instance of Fee Schedules. The client should not generate the hash key value. Instead, the client should query on the Fee Schedules collection resource with a filter on the primary key values in order to navigate to a specific instance of Fee Schedules.

    For example: publicSectorFeeSchedules?q=AgencyId=<value1>;FeeScheduleId=<value2>;EffectiveStartDate=<value3>;EffectiveEndDate=<value4>
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
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 : publicSectorFeeSchedules-FeeLine-FeeScheduleMapD-item-response
Type: object
Show Source
Back to Top