vnt_contractusage.contractusage_putbycontractid: Visma.net Financials Package for ContractUsage operations that could not be mapped to a table. |
Response Message has StatusCode NoContent if PUT operation succeed <br></br>Response Message has StatusCode BadRequest if PUT operation failed <br></br>In this endpoint, If-Match can be checked against resource current version when calling with 'erp-api-background' HTTP header.
Parameters of Procedure
The following parameters can be used to control the behaviour of the procedure vnt_contractusage.contractusage_putbycontractid. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example: a `begin package.procedure(value1, value2, value3); end` on a procedure with four parameters will use the default value for the fourth parameter and the specified values for the first three.
Value specification by name is done by listing all values that require a value. For example with `begin package.procedure(name1 => value1, name3 => value3); end` on the same procedure will use the default values for the second and fourth parameters and the specified values for the first and third.
Name |
Data Type |
Required |
Default Value |
Documentation |
|---|---|---|---|---|
p_contractId |
string |
☑ |
|
Identifies the Contract Usage to update |
p_If-Match |
string |
☐ |
|
The If-Match HTTP header allows clients to update a resource only if its current version matches a specific ETag. This mechanism helps prevent conflicts when multiple clients attempt to modify the same resource simultaneously.The If-Match header should be included in the request headers using the following syntax: If-Match: "etag_value"* If the update is successful, the server responds with 204 No Content and includes the new ETag value in the response headers.* If the ETag on the server does not match the value provided in the If-Match header, the server responds with 412 Precondition Failed. |