Transaction matching tables store transactions for matching. You need to define one dataset for each transaction matching table. ‌A dataset links a transaction matching table to a matching group. Several matching groups can use the same dataset, and a single matching group can use many datasets.

Once you've created and configured the client staging and transaction tables, the next step is to create datasets. Use the Datasets form to create and update a dataset, and link it to an existing transaction matching table:

  1. Select Explorer in the navigation pane.
  2. Expand Fluence > Transaction Matching > Maintenance folders, and open the Datasets form.
    To create a new dataset, select Add Row from the Edit menu and fill out these fields in the form:
FieldDescription
DatasetName of your dataset.
TableTransaction table associated with your dataset. Select it from the list of all tables existing in the client schema within the database.
ID Field

Displays the identifier of your transaction table's primary key. Different datasets can have the same transaction ID.
No manual selection is needed for this field.

  • If the transaction table has a primary key, it'll automatically appear under this column.
  • If the transaction table has no primary key, the system will create a new field that automatically increments in value. It'll be called _Identity.

Select Save Data from the Form menu. 

This adds a new row to the Datasets not used in matching rules list. These move to the Datasets used in matching rules list once you associate them with a match group. 

Datasets used in matching rules can't be removed, so to remove a dataset, first make sure that it's been removed from all rule definitions.

You can create multiple datasets from the same transaction table for different use cases. The system has built-in safety measures to recognize existing fields to prevent duplication. Datasets may share the same transaction ID.

Once a transaction table is linked to a dataset, the system will check for two columns: _ImportDate and _MatchId. If these are missing, the system will automatically add them to the table. These columns are essential for matching process and generating matching reports. If you go back to the client transaction table in Configuration, you'll see that the _MatchID and _ImportDate fields won’t be added again. The system has already created them.

Note: Make sure you choose a client transaction table. If you choose a staging table by mistake, it'll add the _MatchID and _ImportDate fields to the staging table. This'll cause errors in Matching when you try to add data to the staging table, as it'll expect those columns. Remember, you will never add data directly to a client transaction table.

Transaction tables with primary keys prevent duplicate transactions. This doesn't apply to tables with automatically increasing fields. Users need to check for duplicates and remove them in the Transactions - Unmatched form.

Select here to view a video on how to create datasets .