Availability
Overview
It is possible to import a list of customers from a CSV (comma separated values) file. The CSV file have to be properly formatted with a character, such as a comma, used to separate the data. The import wizard provides sample CSV files that can be downloaded and used as a guide. It is a good idea to have a test run with a limited number of rows in the file before moving to massive import.
During import, new activities are created with a parent-child hierarchy specified in the CSV file. They cannot be added as new subactivities to existing parent activities or projects.
In this article
Requirements
The minimum permissions required for importing activities are the "Manage system settings" global permission and the "Add activities" permission for the user's project access level (when importing into projects where the user is a member) or non-project member global permissions (when the user is not a member of the destination project).
Important
It is not possible to update existing activities during the import process, e.g. by matching IDs or names in the CSV file; all imported activities are added as new ones. For all imported activities unique IDs are generated during import.
Import wizard
You can have activities stored as a CSV file imported to Birdview PSA using a wizard.
To be imported to Birdview PSA, a CSV file should have values in their respective places and separated by a list separator (default is a comma). An example of CSV file fields:
- Activity name
- Activity description
- ID
- Parent ID
- Estimated duration
- Start date
- End date
A portion of a source CSV file might look like this:
Activity name;Description;ID;ParentID;Duration;Start date;End date
Configure;activity1;20;;25;6/5/2007;6/20/2007
Develop;activity2;21;;30;6/5/2007;6/18/2007
Test;activity3;22;;40;6/5/2007;6/17/2007
As you can see, the first line contains the names of fields the values correspond to. Whilst it is useful for some purposes, it may wreak havoc during import. For this reason, you will have the option to skip the first line while importing data from a CSV file.
Importing a list of activities
To import a group of activities stored in a CSV file, follow these steps:
- Go to Activity Center | More actions (
) | Import from CSV.
- Select Tasks from the "Import list of" drop-down list.
- In the Default project field, select the project you want to import the tasks to.
- Click "Browse" opposite the "Select CSV file:" field, and find the source CSV file.
- In the Field separator field, select a field separator used in the CSV file (comma and semicolon are the most common separator).
- Select the Skip first line of the file checkbox (refer to the second note above)
- Click "Next".
- Perform field mapping, i.e. link fields of activities being imported with Birdview ones, including custom fields. Use "Add field" to add new fields for mapping.
- Use "Reset fields" if you have made a mistake adding fields.
- Click "Import".
You will get the message ‘Import completed. X records were imported successfully.' if import has been successful.
Note
You can import both native and custom fields through the CSV function.
Importing activities to multiple projects
The activity import procedure described above covers the case where ALL activities imported from a CSV file are assigned to a single project in Birdview PSA. If you need to import activities so that they automatically assigned to their respective projects in Birdview PSA, you need to take additional steps to make sure the import is successful.
- Make sure the source CSV file contains a column "Project name" and includes the names of projects the activities being imported belong to.
- Go to Activity Center | More actions (
) | Import from CSV
- Select Tasks from the "Import list of" drop-down list.
- In the Default project field, select the project you want to import the tasks to if the "Project name" field is empty.
- Click "Browse" opposite the "Select CSV file:" field, and find the source CSV file.
- In the Field separator field, select a field separator used in the CSV file (comma and semicolon are the most common separator).
- Select the Skip first line of the file checkbox (refer to the second note above)
- Click "Next".
- Perform field mapping, i.e. link fields of both projects and activities being imported with Birdview ones, including custom fields. Use "Add field" to add new fields for mapping.
- Click "Import".
You will get a message ‘Import completed. X records were imported successfully.’ if import has been successful.
Note on notifications
Since this operation can generate potentially a great many changes in your system of projects and activities, resulting in a massive influx of incoming letters, the notifications are automatically disabled during the import of activities from a CSV file.
Note on ID and ParentID
The import routine cannot use existing ID numbers. When importing activities, Birdview PSA will not keep the IDs you’ve manually inserted under the ID and ParentID column but replace them with next available instead. However, these columns are used during import should you wish to have two or more of the imported activities be in the parent-child relationship, as shown by their corresponding ID and ParentID numbers, i.e. when ID value of one activity is equal to the value in the ParentID column of one or more other ones (child, or sub-, activities) being imported, they will remain such once imported.
In the example below, the activity IDs and Parent IDs entered will not be maintained as shown once the activities are imported, but the "Gantt Chart" will be made a sub-activity of the "Writing Progress Report", using the next available activity ID’s generated by the system.
Activity name;Description;ID;ParentID;Duration;Start date;End date
Writing Progress Report;NCSA Quarterly Report;567;;25;6/5/2007;6/20/2007
Gantt Chart;Developing Gantt Chart;569;567;25;6/12/2007;6/15/2007
The "Gantt Chart" activity will be imported as a sub-activity of the "Writing Progress Report" one by virtue of its ParentID being equal to the other’s ID (567).
Note
If you are planning to import a large set of data, it's always best to do a test import, with just a few lines of data and if it looks ok then do the rest. To do things this way, you will want to split your CSV into two files, 1st with just a few records and 2nd file with the rest. Do the test on the 1st file and then do the full import on the 2nd file.