Project import - Visma L7/LTR

Projects can be imported to the service from Visma L7. Import uses REST api provided by Visma.

In Visma L7 projects are in three levels:

1. Company number
2. Main number
3. Sub number

For example

• 100001 - Yritys Oy
  
  • 5432 - Tuotekehitys
    
    • 110205 - Ohjelmointi

Importing company number to Nepton is optional and can be defined in settings. More about this below.

Note that if you are migrating from old SFTP-import to new REST-api solution, SFTP-import must be run once before switching the interface so that project identifiers are updated so that they are supported by REST api correctly.

If project already exists in Nepton, its information is updated. If project's (subnumber) state (orderStatus -information) value is something else than 8 (completed) or 9 (locked), project end date is set empty so that they are available for event recordings. Project start date is set as empty in the import.

Configuration

1. Configuring basic settings

Basic settings can be defined in working community settings, Worktime > Administration > Working community settings > Integrations > Projects >Visma L7 project import

At least the following settings must be configured so that projects can be imported from Visma L7 API:

If you don't know what to set in the following fields:

• API settings > Import web service address
• API settings > Company hash
• API settings > API token

Contact your Visma supporting person.

Other configurations for import:

Project import can use multiple Visma REST api sources. Each source requires their own:

• Import web service address
• Company hash
• API token
• Parent project for imported projects
• Person used to create projects

When multiple sources are used, it must be checked that company numbers and main numbers are unique between sources. Otherwise one source can overwrite projects imported from another source.

2. Configuring person identifiers

If also project managers need to be set in the import, person identifiers must be set in Employees > Person's information > Identifiers -view. If persons Visma identifier is not set, employee number is used as an identifier.

Technical functionality of import

Limitations

• If company numbers are set to be imported, empty company numbers are not imported. If company number is not imported in this case, its main or sub number are not imported either.
• Main numbers with empty number are not imported. In this case its sub number is not imported either.
• Sub numbers with empty number are not imported.

Authentication

Company hash and API token are send in HTTP headers. Company hash is sent as HTTP header hash and API token in HTTP header token.

Scheduling import

Scheduling settings can be found in Worktime > Administration > Working community settings > Integrations > Scheduling > Integration scheduling.

Visma L7 schedule can be done on either with minutely (e.g. every 15 minutes, every hour etc.) or daily interval. Select one of the 'Visma L7 project import #{number}' selections from the Integration dropdown. Dropdown shows a selection for each interface source configured for import. This means that a schedule needs to be configured separately for each source, but in this way you can define an individual schedule for each source.

Read more about configuring schedules here.

Expected responses

/projects/ end point

Response is expected to be in JSON format. For this an HTTP header is sent as Accept: application/json.

End point is used only to import main numbers. Sub numbers are imported from /salesorder/ end point.

Example response

{
  "project": [
    {
      "rec": "1",
      "mainNumber": "000001",
      "mainNumberName": "Turku",
      "mainNumbercostCentre": "1000",
      "mainNumbercostCentreName": "MYYNTI",
      "mainNumbersalesMan": "5000",
      "mainNumbersalesManName": "Matti Myyjä",
      "mainNumberworkQuality": "",
      "mainNumberworkQualityName": "",
      "subNumber": "1",
      "subNumberName": "Projektin aloitustyö",
      "subNumberCostCentre": "1000",
      "subNumberCostCentreName": "MYYNTI",
      "subNumberType": "1001",
      "subNumberTypeName": "Myyntitilaus",
      "subNumberOrderDate": "",
      "partyByNumber": "100027",
      "partyByBusinessId": "1234567-7",
      "partyByName1": "Yritys Oy",
      "deleted": "0"
    }
  ]
}

/salesorders/ end point

Response is expected to be in JSON format. For this an HTTP header is sent as Accept: application/json.

Example response

{
  "salesorder": [
    {
      "rec": "1",
      "orderNumber": "000001",
      "subNumber": "1",
      "orderType": "1",
      "orderTypeName": "Myyntitilaus",
      "orderName": "Projektin aloitustyö",
      "currency": "EUR",
      "costCentre": "1000",
      "orderDate": "",
      "deliveryDate": "2023-11-23",
      "paymentTerms": "30 pv netto",
      "deliveryTermsCode": "",
      "deliveryTerms": "",
      "deliveryMethodCode": "",
      "deliveryMethod": "",
      "orderStatus": "1",
      "mainOrderType": "1",
      "mainOrderTypeName": "Myyntitilaus",
      "mainOrderCostCentre": "1000",
      "mainOrderCostCentreName": "MYYNTI",
      "party1Rec": "1057",
      "party1Type": "BY",
      "party1BusinessId": "1234567-7",
      "party1CompanyNumber": "100027",
      "party1Name1": "Yritys Oy",
      "party1Name2": "",
      "party1visitAddress": "Osoite 1",
      "party1postalAddress": "",
      "party1postalZip": "00000",
      "party1postalCity": "PAIKKAKUNTA",
      "party1countryCode": "FI",
      "party1countryName": "Suomi",
      "party1PersonName": "Antti Asiakas",
      "party1ContactNumber1": "",
      "party1ContactNumber2": "",
      "party2Rec": "1058",
      "party2Type": "DP",
      "party2BusinessId": "1234567-7",
      "party2CompanyNumber": "100027",
      "party2Name1": "Yritys Oy",
      "party2Name2": "",
      "party2visitAddress": "Osoite 1",
      "party2postalAddress": "",
      "party2postalZip": "00000",
      "party2postalCity": "PAIKKAKUNTA",
      "party2countryCode": "FI",
      "party2countryName": "Suomi",
      "party2PersonName": "",
      "party2ContactNumber1": "",
      "party2ContactNumber2": "",
      "subNrStatus": "avoin",
      "projectWorkQuality": "",
      "orderNrCostcentre": "1000",
      "orderNrCCName": "MYYNTI",
      "orderNrName": "",
      "modifiedTs": "2023-05-26 12:57:02",
      "deleted": "0"
    }
  ]
}

Import from SFTP-server

Note! REST API solution described above is the recommended method for importing projects.

Project information must be formed in text format files to the SFTP-server. Settings can be found in Worktime > Administration > Working community settings > Integrations > Visma. All files from the set SFTP-server are handled, so material can be split into separate files.

File must be saved with ISO-8859-1 character encoding. Fields must be separated with a pipe (|). Line break can be in either Windows- (CR+LF) or UNIX-format (LF).

File does not include header row. In the file each L7 main number or L7 sub number is transferred in its own row. File can include both main numbers and sub numbers. Main number must be present in the file before sub number.

Imported projects are formed into the service automatically. If project already exists in Nepton, its information is updated. If project's (subnumber) state (project status -field) value is something else than 8 (completed) or 9 (locked), project end date is set empty so that they are available for event recordings. Project start date is set as empty in the import.

Scheduling SFTP import

Scheduling settings can be found in Worktime > Administration > Working community settings > Integrations > Scheduling > Integration scheduling.

SFTP-import schedule can be done on either with minutely (e.g. every 15 minutes, every hour etc.) or daily interval. Select 'Visma L7 project import (old)' from the Integration dropdown.

Read more about configuring schedules here.

Row type main number

Row type sub number