This version of the software is currently available only to customers in the Controlled Availability (CA) program.

Browsing and filtering form or table mappings

The Data Mapping interface shows the list of all form or table mappings in the data mapping.

DataMapping.png

The table shows the following icons for the mapping status:

Icon

Definition

YellowCheckMark.png

OK—The mappings do not have issues.

GrayCheckMark.png

Ignore—There are one or more errors or warnings that are marked as Ignorable.

ExclamationPointMark.png

Warning—There are one or more warnings affecting field mappings.

XMark.png

Error—There are one or more errors.

The following fields appear for the mapping you select.

Field

Description

Mapping Status

The mapping status. Select one of the following values to filter the results:

  • Mapped—Form or table mappings that have a source form or table successfully mapped to a target form or table.
  • Source Not Mapped—Forms or tables that are in the migration tree but are not mapped to a form or table in the source version.
  • Target Not Mapped—Forms or tables that are in the migration tree but are not mapped to a form or table in the target version.
  • Any Issue—Forms or tables that are from the Source and Target Not Mapped categories.

Source

The sources are set to:

  • Auto if BMC Helix Data Manager Expert automatically mapped the fields.
  • Manual if the mapping was changed with the BMC Helix Data Manager Workbench.

Match on Fields

BMC Helix Data Manager can match and update records in the target system on any defined Match On keys. These are fields in the imported data set that must match fields in the target data set for a record to be updated rather than created.

For Remedy application types, the default Match On Key is Request ID; however, for some forms, this may be set to Instance ID or a combination of fields. BMC Helix Data Manager automatically checks for and matches NULL values in the Match On Key field if the field is not Request ID (1) or Instance ID (179) and is not a required field.

If matching on any other value than Request ID, BMC Helix Data Manager automatically transforms the Request ID so it does not clash with records in the target system by adding a BMC Helix Data Manager prefix. For example, "000000000012345" is be transformed to "A00000000012345".

Import Action

Available options are:

  • Create—Using the Match On Fields criteria, a new record will be created for each imported record that does not match a record in the target system.
  • Modify All Matching Records—Using the Match On Fields criteria, existing records will be updated with the imported data.
  • Matching Additional Qualification—Using the Match On Fields criteria, existing records will be updated if the additional qualification is also valid. Records in the imported data set will not be imported unless this criteria also matches.

Qualification

Any data filter for the form or table mapping that is used to extract a subset of the data from the source form or table. This filter is applied in addition to the standard parent-child AR System qualification used when extracting data.

Click the Edit button to add a qualification.

To match fields

The Match On Fields setting indicates the fields that will be used to match records from the source system to records in the target system when importing data. Typically, Match On Fields is set to the Request ID, but for some forms or tables, it might be set to the Instance ID or a combination of fields. If a match is on any other value than Request ID, BMC Helix Data Manager automatically transforms the Request ID so that it does not clash with records in the target system.

Click the Edit button next to the Match On Fields setting to open the dialog box that allows you to add one or more of the fields on the source form to the Match On Field list for this form mapping.

BMC Helix Data Manager automatically matches all fields including NULL values. Request ID (1) and Instance ID (179) are not matched on NULL values.

To ignore unmapped fields

Select Action > Ignore Unmapped Fields button to automatically set the Ignore Errors flag on all unmapped fields on source and target systems.

To view a data mapping

Complete one of the following steps:

  • Open the Data Mapping page from the  Data Migration > Data Mapping navigation menu item.
    The list of all available migration packs are automatically displayed. 
  • Open the migration pack from the Data Migration > Migration Packs navigation menu, and select the migration pack. Then, select Action > View Data Mapping.
  • To view a different migration pack data mapping, click Select, and make a selection.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*