Field mappings

You must have a valid ImportExpress mapping set for each set of files that you want to import.

The mapping set determines how the data is validated and where it is saved in the database. For example, if you indicate that a field in your import file contains construction codes, the import validation process alerts you if any values in that field do not appear to be valid construction codes. If you used custom values in an import field, you can then map the custom values to valid Touchstone values using the Scan Mappings function.

Note: ImportExpress does not import fields that are not mapped to valid Touchstone fields. This provides you with an easy way to identify and omit custom or proprietary data fields that do not affect catastrophe modeling.

After selecting a policy type, a mapping set, and the source files in the Mapping Set and File Selection area, click Edit Mappings to map the fields in your .csv import files to the corresponding Touchstone fields. ImportExpress saves the changes in the mapping set.

When you select the source files for import, ImportExpress automatically attempts to map fields in the files to acceptable Touchstone fields. This function is called automapping.

Workers' compensation records contain the same information as property records, except for information about replacement values and limits. Instead, you map the number of employees, annual payroll, percent of shifts, annual payroll, average annual wage, and medical costs to valid Touchstone fields.