Mapping and transforming fields

The Workbench allows you to control the mapping of data for a selected field.

To map fields

1. From the navigation menu, select Data Migration > Data Mapping.
2. Select a migration pack from the list.
3. Click the Field Mappings tab.
4. Select a field mapping from the list to display the details.

5. On the Field Mapping tab at the bottom of the screen, make any necessary changes.
   Following are the key areas of the display:

   • Target Field—Shows the target field into which data will be imported. This will always be displayed unless an unmapped source field is selected.
   • Source—The data source for the field mapping. BMC Helix Data Manager supports the following data source types:
     • 
       
       • Source Field—The data is imported from the selected Field from the source Form
       • Constant—A constant value which is provided in BMC Helix Data Manager
       • Data Enrichment—Data comes from another Form or a spreadsheet uploaded to BMC Helix Data Manager
       • Conditional—Allows one or more distinct field mappings which will be used when the source record meets different AR System qualification criteria
       • Custom—Allow a custom mapping type to be created.
       • None—No mapping is configured for this field
   • Transform—Allows data transformations to be applied to the data value returned by the Source mapping.
   • Enums—This tab shows the mapping for enumerated fields.

   The following example shows the field mapping for the AAS Template ID Previous field, which is the Request ID for the AAS:Template form. The mapping is between the Request ID on both forms, and the Request ID Transform is being automatically applied with the transformation configured at the time of migration.
   

6. To ignore any problems with the selected field or enumerated mappings, select the Ignore Issues check box.
7. Click Save.

To browse field mappings

1. From the navigation menu, select Data Migration > Data Mapping.
2. Select a form mapping, and click the Field Mappings tab.
   The following example shows the Field list filtered to show only issues, which are designated with  on the Field Mapping tab.
   

To configure the source for a target field

To change the source for a selected target field, select the target field from the list of field mappings and open the Source list.

To configure a conditional mapping for a target field

The conditional source type allows you to create multiple alternative field mappings that will apply when the record being migrated matches a criteria defined as an AR System qualification.

1. Select the field mapping from the list.
2. On the Field Mapping tab, select Conditional from the Source menu.
3. Click Save.
   After the field mapping is updated in the repository, the view is updated to show the list of possible field mappings and the associated qualifications.
   Initially, only one field mapping is configured (a fallback mapping). This mapping is applied if no other criteria are matched. The fallback mapping is copied from the initial field mapping before it was set to have a conditional source.
   The example shows a conditional mapping with a fallback mapping and an additional mapping that will be used if the Status of the record being migrated is > 3. You may create additional conditional mappings by clicking the Add button.
4. Select a mapping from the list to view and manage the settings.
   Conditional mappings are listed with a sequence number. BMC Helix Data Manager processes conditional mappings in descending order, so the qualifications with the highest sequence number are assessed first. When a conditional qualification is true, no further processing occurs on that individual record.

To disable a conditional mapping

1. Open the Source menu, and select Another Mapping.
2. Click Save.
   The selected field mapping reverts to the fallback mapping.

To create a custom mapping

1. Select the field mapping from the list.
2. On the Field Mapping tab, select Custom from the Source menu.

3. Enter a qualification.
   You can perform string concatenations and to mix and match source fields, data enrichments, and transforms.

   Custom mapping types are not validated. They are considered an advanced option.

4. Click Save.

Configuring transformations for a field

The following options are available for transforming the data in a field as part of data migration. You can select these options from the Transform list on the Field Mapping form.

Selecting a custom function

You can select a custom function as a special type of transform for a field. You can apply any defined database function to transform a field. To indicate the position of the original field value in the database function, use a question mark (?). For example, if you want to call a function to round a number to 2 digits, the custom function call would be as follows:

ROUND(?,2)

You can create custom functions to apply complex transformations to field values.

Managing enumerated mappings for a field

The Enum Mapping tab lists fields with enumerated values. The following example shows the mapping for a Status field with one enum mapping flagged as a warning because the spelling of the enumerated value text is "Canceled" in the source system and "Cancelled" in the target.

The following icons illustrate the status of the enum mapping in the table:

Errors and warnings cascade up to the field mapping. For example, a field mapping with a warning and an error in the enumerated mappings show with an error status.

To ignore enumerated warnings and errors, select the Ignore Mapping Problems check box on the Field Mapping tab.

To remap an enumerated mapping, select the enumerated mapping and click the source or target Select button to open the list of available enumerated values. Select a value from the list and click Select. Then, click Save to update the mapping.