# Inventories Gets an inventory summary for inventory items. Sample request: GET /inventory?inventoryId=Item1 GET /inventory?warehouseId=MAIN&modifiedSince=2021-08-01T12:00:00&modifiedSinceCondition=>&pageSize=1000 If modifiedSinceCondition is not specified, it defaults to >=. If modifiedSince is not specified, it defaults to 1900-01-01. If expand with lotSerial, only the lotSerial numbers that has quantity will be included in the response. GET /inventory?inventoryId=Item1&InventoryId=Item2&expand=location,attribute,lotSerial GET /inventory?expand=location&attributeFilter=WEBSHOP:1 ## Documentation Sample request: GET /inventory?inventoryId=Item1 GET /inventory?warehouseId=MAIN&modifiedSince=2021-08-01T12:00:00&modifiedSinceCondition=>&pageSize=1000 If modifiedSinceCondition is not specified, it defaults to >=. If modifiedSince is not specified, it defaults to 1900-01-01. If expand with lotSerial, only the lotSerial numbers that has quantity will be included in the response. GET /inventory?inventoryId=Item1&InventoryId=Item2&expand=location,attribute,lotSerial GET /inventory?expand=location&attributeFilter=WEBSHOP:1 - Catalog: `NgSalesOrders` - Schema: `Inventory` This is a read-only table function. The Visma.net Financials API may not support changing the data or the Invantive UniversalSQL driver for Visma.net Financials does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Visma.net Financials API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `Inventories`. 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 `select * from table(value1, value2, value3)` on a table 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 `select * from table(name1 => value1, name3 => value3)` on the same table 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 | |---|:---:|:---:|:---:|---| | `modifiedSinceCondition` | `` | ☐ | | Condition used in filtering when an inventory item's warehouse or location availability last changed | | `modifiedSince` | `` | ☐ | | A date/time value for filtering when an inventory item's warehouse or location availability last changed Unless a specific time zone offset is included (e.g. '2012-12-24T12:15:14+02:00'), the date is considered to be in the UTC time zone. | ## Columns of Table Function The columns of the table function `Inventories` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `COMPANY_CODE` | `varchar2(30)` | Company Code | ☑ | Partition code, segmenting the data. | | `COMPANY_NAME` | `varchar2(240)` | Company Name | ☑ | Name of the partition. | | `attributes` | `varchar2` | | ☐ | Attributes applied to the inventory item The JSON text of the nested object. | | `baseUnit` | `varchar2` | Base Unit | ☐ | The base unit for the inventory item | | `description` | `varchar2` | Description | ☐ | The description of the inventory item | | `internalId` | `int32` | Internal ID | ☐ | The internal Id used by the system to identify the inventory item | | `inventoryId` | `varchar2` | Inventory ID | ☐ | The inventory id (InventoryCd) |