# Defining Profile Maps Often, the source data does not match the data in ASM exactly for static values that are being passed. It used to be necessary to ensure the data coming from the source system matched what was in the destination system exactly or the import/matching would fail. ASM has a Profile mapping feature that makes this problem obsolete. For example, a criticality value of “Very High” on an external resource can be set to a criticality value of “Priority 1” in ASM Core through **Profile Mapping.** ## **Setup a Profile Map** 1. Select the **Details** tab and add the name and, optionally, a description of the profile map. 2. Select the **Map** tab and choose the external resource fields to be mapped to the ASM Core field: * Click the question mark (?) to select the external field. The internal field selected is shown after the arrow. * On the following line, select an operator, such as equals to (=) and pick or set a value defined for the external field. * Next to this, pick the corresponding value defined for the ASM Core field, which must be used when the external field is set to the value chosen. * Repeat for each value in the external field. * Use the up and down arrows to change the priority of the value mappings. 3. Select the **Behavior** tab and specify the default field mapping should the mapped values not be met, including if no match is found between the internal field (profile) value and the external field: * If an external field value is not mapped to an internal field value, select **Find value in profile matching the value of field**. Click and set the external field to match to the internal field by default. * If the external field value cannot be matched to the internal field value, select an option:
Default to profile value:uses the internal field value specified here. Click to pick a profile value.
Create new profile value:creates a new value for the internal field.
4. Click **OK** to save the profile map.