Navigation: Catalog: Fortnox > Schemas > Schema: Warehouse_IncomingGoods > Tables

IncomingGoodDocuments

List Incoming Goods DocumentsList incoming goods documents matching the given parameters.Sortable fields:id,has_delivery_note,delivery_note_id,supplier_number,date

Catalog: Fortnox

Schema: Warehouse_IncomingGoods

Primary Keys: id

Label: {res:itgen_fnx_incominggooddocuments_plural}

Retrieve: true

Insert: true

Update: true

Delete: false

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function IncomingGoodDocuments. 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	Documentation
completed	boolean	☐	`true` to include only completed documents.`false` to include only non-completed documents.
deliveryNote	string	☐	Include only documents where `deliveryNote`-field contains the given text (case-insensitive).
financialyear	int64	☐	Selects what financial year that should be used (does not work on every table).
financialyeardate	datetime	☐	Selects by date, what financial year that should be used (does not work on every table).
fromdate	datetime	☐	Defines a selection based on a start date. Only available for invoices, orders, offers, vouchers and supplierinvoices (does not work on every table).
itemId	string	☐	Include only documents with the given `itemId`.
lastmodified	datetime	☐	Retrieves all records since the provided timestamp (does not work on every table).
note	string	☐	Include only documents where `note`-field contains the given text (case-insensitive).
q	string	☐	Include only documents where `id` or `deliveryNote`-field contains the given text (case-insensitive).
released	boolean	☐	`true` to include only released documents.`false` to include only non-released documents.
supplierNumber	string	☐	Include only documents with the given `supplierNumber`.
todate	datetime	☐	Defines a selection based on an end date. Only available for invoices, orders, offers, vouchers and supplierinvoices (does not work on every table).
voided	boolean	☐	`true` to include only voided documents.`false` to include only non-voided documents.

Columns of Table Function

The columns of the table function IncomingGoodDocuments are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

Name	Data Type	Label	Required
completed	boolean	{res:itgen_fnx_completed}	☐
date	datetime	{res:itgen_fnx_date}	☐
deliveryNoteId	string	{res:itgen_fnx_deliverynoteid}	☐
hasDeliveryNote	boolean	{res:itgen_fnx_hasdeliverynote}	☐
id	int64	{res:itgen_fnx_id}	☐
note	string	{res:itgen_fnx_note}	☐
released	boolean	{res:itgen_fnx_released}	☐
stockPointId	guid	{res:itgen_fnx_stockpointid}	☐
supplierName	string	{res:itgen_fnx_suppliername}	☐
supplierNumber	string	{res:itgen_fnx_suppliernumber}	☐
unmatchedValue	decimal	{res:itgen_fnx_unmatchedvalue}	☐
voided	boolean	{res:itgen_fnx_voided}	☐

03-06-2025 18:15 Version 24.1.110-BETA+5438

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Fortnox API Data Model

IncomingGoodDocuments

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information