Importing Match Types

When importing a match type that contains one or more group attributes:

  • If your application does not contain a group attribute with the same name as that in the import file, the group attributes (including values) are imported.
  • If your application contains a group attribute with the same name as that in the import file, and this group attribute is not used by any other match type, the members and values are replaced with those in the import file.

Note:

When migrating from a test environment to a production environment, it is recommended that you keep group attributes up to date.

To import match types:

  1. From the Home page, click Application, and then Match Types.
  2. Click Import.
  3. In the Import Match Type dialog, click <Select a File>, select the file containing the match type to be imported, and then click Open.
  4. Click Import.

    If a match type with the same name as the one being imported exists in the application, then a Warning dialog appears. Click Yes update the definition of the existing match type using the one being imported.

    A message advises that the match type has been successfully imported.

  5. In the Import Match Type dialog, click Close.
  6. On the Match Types screen, click Refresh.
  7. When the import is complete, the Status on the Match Types screen is set to Approved.

If you want to use a match type as a template to create other match types, you can first create this match type, export it to a file, import the match type multiple times into your application, and then update the imported match types as required. However, because you cannot import a match type with the same name as an existing match type, you can create the match type, export it to a file, rename the match type in the application, and then import it to create other match types. For example, you create a match type named Bank_template that will be used to create other match types and then export this match type. In your application, rename Bank_template to Bank. Then, import Bank_template into your application and edit its ID, name, and other properties as required. If you need to create more match types, repeat the import process.

Importing Match Types And Data Integration Applications

When importing an existing match type, if the ID of a data source attribute in the import file is different from the ID of the data source attribute in the match type, then the data source attribute ID is updated to use the ID in the import file. However, in Data Integration, Transaction Matching target applications that are associated with this match type are not automatically updated. The existing dimensions are retained and a new dimension is created, using the name of the updated data source attribute ID. The Service Administrator must map the new dimension to the correct source.

For example, the match type Intercompany contains a data source attribute with ID Bank_Ref. The import file uses Bank_Reference as the data source attribute ID for the Intercompany match type. When you import the Intercompany match type using the import file, the data source attribute ID is updated to Bank_Reference. In Data Integration, Transaction Matching target applications that are associated with Intercompany will still contain the Bank_Ref dimension and its source mapping. A new dimension named Bank_Reference is created. The Service Administrator must map Bank_Reference to the correct source.