Purchase orders association
Use the purchase_orders association to retrieve information about
purchase orders associated to the contracts.
Syntax
<URL>?columns[]=purchase_orders.<column>&token=<token>
Available columns
| Column name | Description | Displayed by default | Type |
|---|---|---|---|
| purchase_number | Identifier of a purchase order. Purchase numbers must be unique for a given contract. For the existing contracts, uniqueness of this value is enforced when editing a contract. | ✓ | String |
| document_link | Document link of the purchase order. This value is optional. | String | |
| vendor | Vendor of the purchase order. This value is optional. | String | |
| quantity | Value of the purchase order. -1 means ELA and positive integer means a quantity
of the purchase order. A special value ELA (Enterprise License Agreement) for purchase order value is added. It means unlimited number of licenses for a given entitlement period. |
✓ | Integer |
| The expense of the purchase order. The column accepts non-negative floating
value with at most 2 decimal places. This value is optional. |
✓ | Float | |
| The cost center to which the purchase order belongs to. This value is optional. |
✓ | String | |
| The project to which the purchase order belongs to. This value is optional. |
✓ | String | |
| entitlement_start | Entitlement start date of the purchase order. Note: The
allowed format is "YYYY-MM-DD", for example "2019-01-31". Value "9999-12-31" in
REST API represents "Never" on UI. |
✓ | String |
| entitlement_end | Entitlement end date of the purchase order. This value is optional. Note: Allowed format is "YYYY-MM-DD", for example, "2019-03-31".
Value "9999-12-31" in REST API represents "Never" on UI. |
✓ | String |