Please enable JavaScript to view this site.

Made in EU
Visma.net Financials Forums

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

ProjectTaskAttributesByInternalId

Get project task information by internal id.Data for a single project task. The response headers include an ETag after a successful GET operation.

Catalog: VismaNet

Schema: ProjectTask

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 ProjectTaskAttributesByInternalId. 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

internalId

 

☑

 

The organisation code.

 

Columns of Table Function

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

Name

Data Type

Label

Required

Documentation

branch_name

varchar2

Branch Name

☐

Click the magnifier. > The name.

branch_number

varchar2

Branch Number

☐

Click the magnifier. > The identifier.

COMPANY_CODE

varchar2(30)

Company Code

☑

Partition code, segmenting the data.

COMPANY_NAME

varchar2(240)

Company Name

☑

Name of the partition.

createdDateTime

datetime

Created

☐

Information collected from the system. Not visible on the screen.

defAccount_description

varchar2

Default Account Description

☐

Name of item/description

defAccount_number

varchar2

Default Account Number

☐

Number of item

defAccount_type

varchar2

Default Account Type

☐

 

defAccrualAccount_description

varchar2

Default Accrual Account Description

☐

Name of item/description

defAccrualAccount_number

varchar2

Default Accrual Account Number

☐

Number of item

defAccrualAccount_type

varchar2

Default Accrual Account Type

☐

 

defAccrualSub_active

char

Default Accrual Account Sub Active

☐

 

defAccrualSub_description

varchar2

Default Accrual Account Sub Description

☐

Click on the magnifier. > The description.

defAccrualSub_id

varchar2

Default Accrual Account Sub ID

☐

Click on the magnifier. > The identifier.

defSub_active

char

Default Sub Active

☐

 

defSub_description

varchar2

Default Sub Description

☐

Click on the magnifier. > The description.

defSub_id

varchar2

Default Sub ID

☐

Click on the magnifier. > The identifier.

description_2

varchar2

Description 2

☐

Mandatory field: Description > The description of the task.

description

varchar2

Description

☐

Attribute > The description of the attribute.

endDate

datetime

End Date

☐

End date > The date when the task was actually finished.

id

varchar2

ID

☐

 

internalId

int32

Internal ID

☐

Internal ID* > The internal ID of the task.

lastModifiedDateTime

datetime

Last Modified

☐

Information collected from system.

plannedEnd

datetime

 

☐

 

plannedStart

datetime

 

☐

 

projectInternalId

int32

 

☐

Project Internal ID* > The internal ID of the project.

rateTable_description

varchar2

Rate Table Description

☐

Click on the magnifier. > The description.

rateTable_id

varchar2

Rate Table ID

☐

Click on the magnifier. > The identifier.

restrictEmployees

char

Restrict Employees

☐

Summary tab > Task properties section > Restrict employees > A check box that indicates (if selected) that only the employees listed on the Employees tab of this window can create activities and documents associated with the current task.

startDate

datetime

Start Date

☐

Start date > The date when the task was actually started.

status

varchar2

Status

☐

Mandatory field: Status* > The status of the task, which can be one of the following: In planning, Active, Cancelled, Completed.

taskId

varchar2

Task ID

☐

Mandatory field: > Task ID* > The ID of the task.

taxCategory_description

varchar2

 

☐

Name of item/description

taxCategory_number

varchar2

 

☐

Number of item

timeStamp

blob

Timestamp

☐

Identifier that represents a specific version of the resource.It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)

value

varchar2

Value

☐

Value > The value of the attribute.

visibility_visibleInAp

char

 

☐

Supplier ledger

visibility_visibleInAr

char

 

☐

Customer ledger

visibility_visibleInCa

char

 

☐

Cash management

visibility_visibleInCr

char

 

☐

 

visibility_visibleInEa

char

 

☐

Expenses

visibility_visibleInGl

char

 

☐

General ledger

visibility_visibleInIn

char

 

☐

Inventory

visibility_visibleInPo

char

 

☐

Purchases

visibility_visibleInSo

char

 

☐

Sales

visibility_visibleInTa

char

 

☐

Time entries

 

X

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.

  
Disclaimer