Importing and Exporting Resources

To ease the process of adding resources and resource teams to your system, you can import them from a spreadsheet. The information in the spreadsheet can come from an external system, such as an Active Directory store or other Lightweight Directory Access Protocol (LDAP) providers, or you can manually create a spreadsheet as long as it meets the requirements discussed in the following sections.

Use the import feature to:

Steps for Importing Resources

Use these basic steps to import resources:

  1. In Application Administrator, click the Resources icon on the Administrator portal, and then click Import/Export.
  2. Export a resource spreadsheet template. For details, refer to Export Resources Page.
  3. Add data to the spreadsheet using the information in:
  4. Select the Import tab, and then import the spreadsheet.
  5. Review the import log. For details, refer to Import Log.

Spreadsheet Requirements

The spreadsheet used to import resource teams and resources must adhere to certain requirements:

Tip: The easiest way to prepare a spreadsheet is to first perform an export. You can use the empty spreadsheet as a starting point for meeting the following requirements.

Preparing the Resources Sheet

Each column represents a resource attribute. The information in this section describes the relationships between those attributes, as well as guidance on which are required, which are used for uniqueness checking, and data rules.

Each row represents a resource. Each resource may have multiple rows, depending on the number of teams the resource is assigned to.

Use the following information to prepare the Resources page of the spreadsheet.
Note: Rows that contain invalid date are skipped during the import process. Review the log for details regarding skipped rows.

Preparing the Teams Sheet

Resource teams must exist in the system or be imported with resources before they can be assigned to resources during an import.

Columns represent general resource team settings: name, description, and parent. Each row represents a single resource team.

Use the following information to prepare the Teams page of the spreadsheet.

The Team Name and Parent columns are used for uniqueness checking. If data does not match existing resource team records for both columns, a new team is added. If row data exactly matches existing data for both columns, the row is skipped.