Navigation: Catalog: VismaNet > Schemas > Schema: ProjectTransaction > Tables

ProjectTransactions: Visma.net Financials Project Transactions

Get a range of Project transaction documents - ScreenId=PM304000

Catalog: VismaNet

Schema: ProjectTransaction

Primary Keys: refNbr

Label: Project Transactions

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 ProjectTransactions. 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
billable	boolean	☐	Filter invoiceable project tasks.
branch	string	☐	Filter on branch for the project transation.
createdDateTime	string	☐	Creation date and time.
createdDateTimeCondition	string	☐	System-retrieved information for state/condition
date	datetime	☐	Filter on the registration date for the project transaction.
expandNote	boolean	☐	Expands project transaction notes
fromPeriod	string	☐	Mandatory. Start date for the task.
greaterThanValue	string	☐	Greater than value. The item which is the object for this, varies from API to API.
lastModifiedDateTime	string	☐	This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present.Accepted format:* ```yyyy-MM-dd```* ```yyyy-MM-dd HH:mm:ss```* ```yyyy-MM-dd HH:mm:ss.FFF```* ```yyyy-MM-ddTHH:mm:ss```* ```yyyy-MM-ddTHH:mm:ss.FFF```_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.
lastModifiedDateTimeCondition	string	☐	This value represents the condition to be applied when retrieving records.Accepted values (without the single quotes):* '>' for greater than* '<' for less than* '>=' for greater than or equal* '<=' for less than or equal_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.
module	string	☐	Select to filter on module; e.g. AR, AP, IN etc. (Values: ModuleGL, ModuleAP, ModuleAR, ModuleCA, ModuleCM, ModuleIN, ModuleSO, ModulePO, ModuleDR, ModuleFA, ModuleEP, ModulePM, ModuleTX, ModuleCR)
project	string	☐	Filter on project ID.
projectTask	string	☐	Filter on Task ID.
status	string	☐	The status of the document. (Values: Hold, Balanced, Released)
toPeriod	string	☐	Mandatory. End date for the task.

Columns of Table Function

The columns of the table function ProjectTransactions 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	Documentation
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
description	string	Description	☐	The top part > Description > The description provided for the transaction.
errorInfo	string	Error Message	☐
metadata_maxPageSize	int64	Metadata Max Pagesize	☐
metadata_totalCount	int64	Total Count	☐
module	string	Module	☐	The top part > Module > The module you create the transactions in.
note	string	Note	☐
origDocNbr	string	Original Document Number	☐	The top part > Orig. doc. no. > The reference number of the underlying document for the transaction.
origDocType	string	Original Document Type	☐	The top part > Orig. doc. no. > The type of the document the transaction is based on. It has one of the following values: Allocation, Time card, Case, Expense claim, Allocation reversal, Reversal, Credit note.
refNbr	string	Reference Number	☐	The top part > Ref. no. > The reference number of the transaction.
status	string	Status	☐	The top part > Status > The status of the transaction. The following statuses are possible: Balanced, Released.

23-06-2025 19:16 Version 24.1.116-BETA+5455

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.

Visma.net Financials API Data Model

ProjectTransactions: Visma.net Financials Project Transactions

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information