Before You Import
Add fields for imported data
Compare the issue data you want to import against the fields in tblDts and tblFixInformation. If you want to import additional issue data for which there are no corresponding fields in these two tables, use the Field editor to add the required fields.
Create a Number field to hold imported IDs or record numbers
If you want to import the IDs or record numbers of your data records, create a numeric field in Vector HelpDesk. You can then map your record IDs to this field when you import your data.
Create users and contacts
Add users and contacts in Vector HelpDesk before importing data that contains user names.
When you import user names into the Owner, Submitter, and Contact fields, the names must match the full names assigned to the users in Vector HelpDesk. You must use the users' full names, not their logon names.
For example, if you import a set of issues owned by a user for whom no entry is defined, the Owner field is left blank.
Note that you can import the numeric ID for a user in the tblUser table (users database).
Customize Vector HelpDesk choice lists to match the imported data
In Vector HelpDesk, customize choice lists to match the values you want to import. You could also change the values in the imported data to match the Vector HelpDesk choice lists. You could do this in the original issue data, or you could use Microsoft Access to modify the source table created when you imported the original issue data.
If you are importing text files
If your issue data is in a text file, the first data record should contain the field names. Otherwise, Vector HelpDesk assigns the fields the names 1, 2, 3, and so on. This makes it harder to map the fields.
Also, the first data record should have no blank fields. Microsoft Access uses the first data record to determine the data types of the fields. For example, if a date field is blank, Microsoft Access imports it as a text value, and you will be unable to convert the field into date format.
Back Up Projects
Make a backup copy of the issue database before you import any data. If you make a mistake mapping the fields, having a backup copy allows you to change the mapping and try again.
Log off users
Make sure no one is using the project database while you import issues. Ask all users to exit Vector HelpDesk before you start to import issues.
Related Topics
Importing Issues into a Source Table
Combining Multiple Source Tables
Importing Issues from Projects