This help document will help you import (s). This document (and the attached sample files) should tell you everything that you need to know about importing files. You should start by testing these in a non-production environment. The sample files that are attached can all be imported with no modifications. And then you can edit them and re-import them to verify that you are able to edit and build importable files. Finally, you should always backupdb your Timesheet database before you begin importing files, especially into your production environment.
The import tools that are included with Timesheet only support importing standard fields and Extra Fields. If you need to use import tools to further setup your Timesheet install, please contact Journyx Professional Services.
This is the general method that we recommend that you folow when you are using the Import Tool.
1. Logged in as an Admin, on the main Admin page click the link for Import Data.
2. On the Import Data page, on the menu on the left, click the link for the import that you would like to run.
3. The screen will refresh to the Import page. On this page you should click the button and browse your system to find the file that you want to import. When you have found the correct file press the button.
4. The screen will refresh with your import file displayed in a grid on the screen. You should examine the file thoroughly to make sure that it is complete and correct.
5. If the file is correct, then click the Admin button in the button bar, and on the main Admin page click the link for Import Data.
6. On the Import Data page, on the menu on the left, click the link for the import that you would like to run.
7. The screen will refresh to the Import page. On this page you should click the button and browse your system to find the file that you want to import. When you have found the correct file press the button.
8. The screen will refresh to a results screen with Messages, Warnings, and Errors. The messages are simply confirmations. There are not normally any warnings. Errors will list each record that did not get imported along with the reason. Generally those reasons are things like “the Employee Number in the import file could not be found”.
9. If you received error messages you can correct those errors in the Timesheet application (adding or correcting Employee Numbers, for instance) or in the import file. You can "chop down" the file to only the previously-rejected records when you re-import it, or you can simply re-import the entire file.
(top)
Most of the time you will be using the button in the Import a file that is located on your computer section and importing a file from your computer. When you are ready to begin importing a file automatically, through the scheduled process, then you need to use the Import a file that is located on the server section to test that the Timesheet application can read files from this location. You might also use this section if your import files are on the server.
When you want to upload a file that is on the server, the Timesheet application itself will be going to get that file. This is different from the browser upload, because in the browser upload option it is really you who is reading the file. This is an important distinction for network security. For the server import (and the scheduled import as well) to work, then the Timesheet application must have the correct permissions to read from the location where your file(s) will be stored. This is why we say that paths to your file that do not contain a drive letter will not work, because the Timesheet application will almost never have permission to read from that location.
If your Timesheet installation is on a Windows server, then it will be the Anonymous IIS account that is trying to read the file for import. The Anonymous IIS account usually does not have read access to most directories, either on or off the server. In that case you will undoubtedly need to get assistance from your Network Administrator to set that up. They will probably suggest changing whatever program that is writing the files to have them written into a folder that the Anonymous IIS user already has permission to read in. This is a great suggestion, and we would recommend the \Journyx\jwt\ps directory for this purpose because this location will get backed up with Timesheet backups.
If your Timesheet installation is on a Unix server, then it will be the account that installed the Timesheet application which will be trying to read the files for import. Your unix server administrator should be able to grant the proper read permissions with no difficulty.
Other than the issue of the Timesheet application's user account having the proper rights to read the file, there are no special issues for the Import a file that is located on the server section of the Import Tool. The and buttons work in exactly the same way as they do in the Import a file that is located on the server section of the Import tool.
(top)
The file that you generate for import must be a simple ASCII flat-file. It must be a delimited-type of file, not fixed-width. The delimiter should be tab, but can be comma. Sometimes a field can have multiple values, which must also be delimited. For instance, the Groups field can contain multiple values. Those multiple values within a field must be comma-delimited, and the entire field must be surrounded by double-quotes. So if you only have a single value in a Groups field then just enter that value and don't worry about it. But if you have multiple values for that field then separate the multiple values by commas and put double-quotes around the field. See the sample files for examples of this.
This table lists each column that you can put into a import file. Your file will not have to contain all of these columns. The "Header" is the name of the field, and is its header in the import file. The "Req." field indicates whether or not the column is required ("Y" = required). If a column is required, then every record (row of the file) must have a valid value in that field. The "Size" field contains the maximum number of characters that are supported within this field. The "#" field is displayed in this chart for ease of reading only, your import file will not have numbers like this.
The table is too large to format into this page. Click here to open it in a separate window suitable for printing.
There are many characters that you should generally not include in your import file. These characters can cause problems in displaying HTML in the web interface, and a few of them can cause database-level errors that can be difficult to recover from. All extended-ASCII characters, like à, ü, and ñ are forbidden.
We generally recommend that you build your files in Excel, just because it is so easy to read and use. If you do use Excel then save it off as a tab-separated-text file, then Excel will add double-quotes around each field that contains a comma. We have found that remembering to remove these double-quotes is difficult, so we have enhanced the import tools to automatically strip double-quote characters from every field, if-and-only-if the double-quotes are the first and last characters in a field. Therefore, in the unlikely event that you want a field to contain and initial and ending double-quote then you will simply have to double your double-quotes, like this: ""doubled double-quotes"" will result in "single double-quotes" being imported. Generally both double-quotes and commas should be avoided except in fields that specify them (like a users' Full Name or the Groups field.)
There is one more odd situation involving commas. In the fields that support multiple values comma-delimited (Groups and Authority), if your Group or Authority name has a comma in it then you are in trouble. Because you end up with something like this, "G1, G2, G,3, G4" (where the name of the third group really contains a comma). In those situations double the comma in the name, like this, "G1, G2, G,,3, G4". The import tool will see and recognize the doubled comma and treat it as a single comma that is part of the name and not as a delimiter. Frankly, if you have a better suggestion for how to handle this we welcome your suggestions at support@journyx.com.
In HTML it is possible to generate extended ASCII characters by using codes. So, if you view the source-code of this page you will see that many characters in the following chart were produced using codes like this: &# 38 to create an &. But & and # are both not-recommended characters. The fact is that they will often import, but sometimes they will display as the character you wish to display and sometimes they will disply as the code itself (&# 38). This is simply a limitation of the cgi script-based nature of the Timesheet application.
All of these characters should be avoided, unless specifically allowed in the Notes on a particular field:
This is generally what your import file will look like. This one is formatted in an HTML table for easy reading. See the downloadable sample files, below, for a more precise file to model yours after.
Right-click on any of these links and select to Save (or 'Save as...') the file onto your local computer. These files are all tab-separated text files. All of the sample files are valid and ready to be imported, recognizing that some of the imports will need to occur in a specific sequence (like importing (s) before you import Memberships.)