Field Mappings

Use Field Mappings to map schedule fields to Touchstone fields.

You need to use field mapping when the field you are importing does not have the same name as the Touchstone field into which you want to import it in Touchstone. For example, the user may name their field Controller in the Scheduling tool; however, the field into which that data must be imported in Touchstone is named Program Manager. You have to tell Touchstone to import the data in the Controller field into the Program Manager field. You do this by mapping the fields.

Touchstone uses a standard import template to import data from schedule projects. However, you can also custom map any data in the project file. For example, you may have a user-defined field or a code field with location information that you want mapped to a Touchstone field.

Field mapping is flexible in that an individual Touchstone field can get its data from any source schedule field. Further, the mappings between source projects may be different. For example, Baseline Start may come from Start1 in Project A and Baseline Start Date in Project B. By mapping the field, you ensure that the data is imported into a common Touchstone field.

The field mappings operate at the project level; that is, each project can have its own field mapping template. This makes it easy to take data from different scheduling tools or submitters and normalize it in Touchstone. You select the template on the Projects Configuration tab.

To use field mapping, do the following:

1. Create a field mapping template.
2. On the template, map schedule fields to Touchstone fields.
3. Assign the template to a project.