Navigation: Schema: ProjectBasic > Tables

BasicProjects: Visma.net Financials Basic Projects

Get a range of Projects - ScreenId=PM301000Request page size must be lower or equal to the allowed max page size which is returned as part of the metadata information.If requested page size is greater than allowed max page size, request will be limited to max page size

Catalog: VismaNet

Schema: ProjectBasic

Label: Basic Projects

The data in this table is partitioned per value of the COMPANY_CODE column.

This is a read-only table function. The Visma.net Financials API may not support changing the data or the Invantive SQL 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 BasicProjects. 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
COMPANY_CODE	string	☐	Partition to retrieve data from.
createdDateTime	string	☐	Creation date and time.
createdDateTimeCondition	string	☐	System-retrieved information for state/condition
description	string	☐	Project name/description
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.
greaterThanValue	string	☐	Greater than value. The item which is the object for this, varies from API to API.
lastModifiedDateTime	string	☐	System generated value for last modification of transaction/record. Use format: YYYY-MM-DD HH:MM (date and time) to filter from date to present.
lastModifiedDateTimeCondition	string	☐	System retrieved information for state/condition.
nonProject	boolean	☐	Set to true to return the non-project.
numberToRead	int32	☐	This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
pageNumber	int32	☐	Pagination parameter. Page number.
pageSize	int32	☐	Pagination parameter. Number of items to be collected.Please use a page size lower or equal to the allowed max page size which is returned as part of the metadata information.If requested page size is greater than allowed max page size, request will be limited to max page size.
projectId	string	☐	Identifies the Project
projectIdDesc	string	☐	Identifies the Project by ID and description
publicId	guid	☐	Identifies the Project by its publicId
restrictedEmployee	string	☐	Id of the employee where access restrictions apply
restrictedUser	int64	☐	Id of the odp user where access restrictions apply
skipRecords	int32	☐	This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
startDate	datetime	☐	Project's start date
status	string	☐	Select project status. (Waarden: Planned, Active, Completed, Cancelled, OnHold, PendingApproval)
visibleInAp	boolean	☐	If the project is visible in the Supplier ledger
visibleInAr	boolean	☐	If the project is visible in the Customer ledger
visibleInCa	boolean	☐	If the project is visible in the Cash management workspace
visibleInCr	boolean	☐	If the project is visible in the CRM workspace
visibleInEa	boolean	☐	If the project is visible in the Expense workspace
visibleInGl	boolean	☐	If the project is visible in the General ledger workspace
visibleInIn	boolean	☐	If the project is visible in the Inventory workspace
visibleInPo	boolean	☐	If the project is visible in the Purchases workspace
visibleInSo	boolean	☐	If the project is visible in the Sales workspace
visibleInTa	boolean	☐	If the project is visible in the Time entities workspace

Columns of Table Function

The columns of the table function BasicProjects are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
autoAllocate	boolean		☐	Summary tab > Invoicing and allocation settings section > Run allocation when you release project transactions > A check box that indicates (if selected) that allocation is run automatically during the release of the documents associated with this project.
automaticReleaseAr	boolean		☐	Summary tab > Invoicing and allocation settings section > Automatically release customer documents > A check box that indicates (if selected) that invoice documents are released automatically after the project invoicing is completed.
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
customer_name	string	Customer Name	☐	Click the magnifier. > The name.
customer_number	string	Customer Number	☐
description	string	Description	☐	Mandatory field: The top part > Description* > The description of the project.
endDate	datetime	End Date	☐	Summary tab > Project properties section > End date > The date when the project is expected to end.
errorInfo	string	Error Message	☐
hold	boolean	Hold	☐	The top part > Hold > A check box that you select to indicate that the project should have the In planning status.
internalID	int32	Internal ID	☐
lastModifiedDateTime	datetime	Last Modified	☐	Systemgenerated information.
metadata_maxPageSize	int64		☐
metadata_totalCount	int64	Total Count	☐
projectID	string	Project ID	☐	Mandatory field: The top part > Project ID* > The unique ID for the project.
publicId	guid	Public ID	☐
startDate	datetime	Start Date	☐	Mandatory field: Summary tab > Project properties section > Start date* > The date when the project starts.
status	string	Status	☐	The top part > Status > The status of the project, which can be one of the following options: In planning, Active, Completed, Suspended, Cancelled.
visibility_visibleInAp	boolean		☐	Supplier ledger
visibility_visibleInAr	boolean		☐	Customer ledger
visibility_visibleInCa	boolean		☐	Cash management
visibility_visibleInCr	boolean		☐
visibility_visibleInEa	boolean		☐	Expenses
visibility_visibleInGl	boolean		☐	General ledger
visibility_visibleInIn	boolean		☐	Inventory
visibility_visibleInPo	boolean		☐	Purchases
visibility_visibleInSo	boolean		☐	Sales
visibility_visibleInTa	boolean		☐	Time entries

22-12-2022 21:03 Version 22.1.101-BETA+3681

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

BasicProjects: Visma.net Financials Basic Projects

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information