Visma.net Financials API Data Model
ExpenseReceipts1: Visma.net Financials Expense Receipts |
Get a range of Expense Receipts, a filter needs to be specified. ScreenId=EP301020
Catalog: VismaNet
Schema: ExpenseReceipt
Label: Expense Receipts
The data in this table is partitioned per value of the COMPANY_CODE column.
Can retrieve data and change data using insert, update and delete.
Select Visma.net Financials API URL: /controller/api/v1/expenseReceipt
Insert Visma.net Financials API URL: /controller/api/v1/expenseReceipt
Update Visma.net Financials API URL: /controller/api/v1/expenseReceipt
Delete Visma.net Financials API URL: /controller/api/v1/expenseReceipt
Field Selection Method: NotRequired
Select Visma.net Financials API Operation: get /controller/api/v1/expenseReceipt
Insert Visma.net Financials API Operation: post /controller/api/v1/expenseReceipt
Update Visma.net Financials API Operation: put /controller/api/v1/expenseReceipt/{receiptNumber}
Delete Visma.net Financials API Operation: delete /controller/api/v1/expenseReceipt/{receiptNumber}
Table Function Parameters
The following parameters can be used to control the behaviour of the table function ExpenseReceipts1. 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 treated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example with `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 |
|---|---|---|---|---|
claimedBy |
string |
☐ |
|
Identifies the employee from the document |
COMPANY_CODE |
string |
☐ |
|
Partition to retrieve data from. |
customer |
string |
☐ |
|
Identifies the customer from the document |
date |
string |
☐ |
|
The date of the document |
dateCondition |
string |
☐ |
|
|
erp-api-background |
string |
☐ |
|
If a URL value is provided, then API endpoint will be queued and executed in background. When the execution of the background operation is finished, the system will POST the response to the specified URL. The endpoint itself responds in this case with a 202-Accepted status and a reference to a state document for the background operation. |
inventory |
string |
☐ |
|
Identifies the inventory item from the document |
invoiceable |
boolean |
☐ |
|
If the document is invoiceable |
project |
string |
☐ |
|
Identifies the project from the document |
projectTask |
string |
☐ |
|
Filter on Task ID. |
status |
string |
☐ |
|
The status of the document. (Values: Open, Pending, Approved, Rejected, Released) |
Table Function Columns
The columns of the table function ExpenseReceipts1 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 or update.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
COMPANY_CODE |
string(30) |
Company Code |
☑ |
Partition code, segmenting the data. |
COMPANY_NAME |
string(240) |
Company Name |
☑ |
Name of the partition. |
requestId |
string |
|
☐ |
|
stateLocation |
string |
|
☐ |
|
27-12-2021 10:59 Version 20.2.169-PROD+3633
