Projects can be handily imported from other services with either a scheduled or manual import. This can be used when for example new projects need to be imported, project information needs to be changed or project needs to be ended.
Attached in the article is an example file for importing project information.
Scheduled import
File containing project information can be scheduled for Nepton to fetch from SFTP - server or API. More information can be found from Scheduled project import - article.
Manual import
For manual project import, person doing the import needs to have both "Administrator" - role and "Kaikki oikeudet" (all permissions) - role for Worktime roles.
Instructions for adding a person: Add person
Instructions for worktime roles: Assigning roles
Preparing data to import
- Use this articles example file as a template.
- Mandatory fields are project name, project code and visibility in a terminal (A, B and H - columns)
- Empty columns must not be deleted. Leave columns empty for fields you do not have information available for.
- When you have filled the information you want to import to service, remove the three top rows from the file (rows 1-3, including A-column's orange text, ’Individual value’ and ’Project Code’).
- Save file in CSV - format - CSV UTF-8 (Comma delimited) (*.csv).
Importing manual file
1. Go to Worktime > Administration > Working community settings > Integration > Project import
2. Select file to import from your computer by clicking Choose file. Locate the CSV-file you have saved previously. Select Import projects.
If import is successful, service shows information about it with green notice text.
If there are projects in the import file that have not changed, they will be marked as skipped projects in the import log.
If import is unsuccessful, service shows information about it with red notice. Also information about errors during import is shown. In this situation the file to import needs to be corrected based on the errors reported by the service. After the file is corrected it can be imported to the service again.
3. Project import is now complete and defined changes or additions to projects have been done.
4. Information about the import can also be found in the service log in Employees - section. Go to Employees > Administration > Service log. Each import is shown as their own row in the log. Detailed information about the import can be viewed by clicking the icon in the left for each row. Icon is green if import has succeeded and red if import has failed.
Imported projects are created to the service automatically. If the project already existed in the service, it's information was updated.
Project's can not be changed with project import. Also project that has a parent project can not be updated as a root project.
Import fields
Field to import | Description |
---|---|
Project Code |
Project code. If a project with this code is not found in the service, new project will be created with this code. If a project with this code is found in the service, that project will be updated.
|
Project Name |
Project name. Mandatory field.
|
Project Description |
Project description. Can be empty.
|
Project Start date |
Project start date, can be empty. Format YYYY-MM-DD. Note: 1.1.1970 and earlier dates are not visible in the user interface
|
Project End date |
Project end date, can be empty. Format YYYY-MM-DD.
|
Parent project code |
Code of parent project, can be empty. The project imported for this row will be set below the project that is set here.
|
ProjectTypeName |
Project type. If empty, default value is 'Projektit' (project_work).
|
Show on terminals |
Is project shown in terminals. '1' means yes, '0' means no.
|