API

Sales APIs

POST sales/project-orders/{projectOrderId}/product-units

Resource for creating a new relation between project order item and product unit

HTTP method POST
URI https://api.rambase.net/sales/project-orders/{projectOrderId}/product-units
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {projectOrderId} Project order identifier
Integer, minimum 100000
Successful HTTP status code 201
API resource identifier 5138, version 1

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<RelatedProductUnit>
2
     <ProjectOrderItem>
3
          <ProjectOrderItemId
ProjectOrderItemId

Required/mandatory field

Project order item identifier

Minimum value: 1

>{Integer}</ProjectOrderItemId>
4
     </ProjectOrderItem>
5
     <ProductUnit>
6
          <ProductUnitId
ProductUnitId

Required/mandatory field

Product unit identifier

Minimum value: 100000

>{Integer}</ProductUnitId>
7
     </ProductUnit>
8
</RelatedProductUnit>
1
{
2
     "relatedProductUnit": {
3
          "projectOrderItem": {
4
               "projectOrderItemId
ProjectOrderItemId

Required/mandatory field

Project order item identifier

Minimum value: 1

": "{Integer}"
5
          },
6
          "productUnit": {
7
               "productUnitId
ProductUnitId

Required/mandatory field

Product unit identifier

Minimum value: 100000

": "{Integer}"
8
          }
9
     }
10
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 100027 HTTP 400 Missing mandatory parameter {0}
Error 101420 HTTP 404 Setting definition not found
Error 107273 HTTP 400 Relation can only be created for products units which are processed (status 8) or deactivated (status 9)
Error 107115 HTTP 400 The relation between this project order item and product unit {0} already exists