Home → Using LincDoc 3.1+ → eForm Administration → Importing an eForm or Document Package

7.17. Importing an eForm or Document Package

You can import previously exported eForm or Document Package files to a new client ID or LincDoc installation using the import option.

Importing the File

Using the import option, select the LincDoc export file that you want to import and start the import process.

  1. Click the admin button, and select import.
  2. The Import dialog box appears.
  3. Click the upload button.
    The Open dialog box appears.
  4. Select the desired export file from your local file system.
  5. Click Open.
    The export file is sent to the LincDoc server and the import process is started.
    If there are no problems found with the import, a message will display informing you that the import was successful. If problems were encountered, proceed to Fixing Import Issues.
  6. Click OK to return to LincDoc.
  7. Make sure to log out and back in to refresh any changes.

Fixing Import Issues

If the import process encounters problems, you'll be presented with a dialog box that enumerates the problems and allows you to choose how to solve them.
 
  1. For each listed issue, choose the solution that suits your needs.
  2. Click the Import button to complete the import process.
  3. After the import process is complete, log out of LincDoc and log back in to refresh any changes made.

About Issue Resolution Options

A resolution list is reported when an item in the import file (a document package, business rule, code list or source document) has the same name as one that is already in the system. For each problem item, your choices to resolve the problem are:

  1. Rename the imported item. This will give the imported item a new, unique name so that it no longer conflicts with the existing item.
  2. Replace the existing item. This will overwrite the existing item with the item in the import file.
  3. Keep the existing item. This will cause import process to skip the item in the import file. The imported document package will use the item that is already in the system.

An example will help to make the choices clearer. Let's say you're importing a new document package that uses a code list called "beverageTypes", which includes the codes "Coffee", "Tea" and "Soda". When you start the import process, a problem is reported, indicating that a code list called beverageTypes already exists in the system. The beverageTypes code list currently in the system includes the codes "Hot", "Dairy", and "Carbonated". If you choose the Rename option, the beverageTypes code list in the import file will be renamed to beverageTypes2. After the import, you will have a beverageTypes code list with "Hot", "Dairy", and "Carbonated", and a beverageTypes2 code list with "Coffee", "Tea" and "Soda". The newly imported document package will use the beverageTypes2 code list. If you choose the Keep option, the beverageTypes code list in the import file will be discarded, and the newly imported document package will use the existing beverageTypes code list with the "Hot", "Dairy", and "Carbonated" codes. If you choose the Replace option, the existing beverageTypes code list will be overwritten with the one in the import file. After the import, you will have a beverageTypes code list with the codes "Coffee", "Tea" and "Soda". Any existing document packages that use the beverageTypes code list will now show "Coffee", "Tea" and "Soda" as the available choices.

This page was: Helpful | Not Helpful
← 27.3. Creating an Email Template