Use the Transaction Duplicate Log report to view a list of all duplicates that occurred during the transaction import. This report filters data based on two parameters: Transaction Table and Duplicates.
Duplicates happen when the same transactions are imported into the system more than once. The system can detect duplicates when the transaction table has a primary key. Once a duplicate is detected, the new import will overwrite the old one if the transaction still needs to be matched. If the transaction is already matched, the new transaction won’t overwrite the old one, and a duplicate will be logged. Duplicates can't be retrieved for transaction tables that don't have a primary key. These tables use an identity field, which can be added afterward.
This form shows generic information, such as the Timestamp, Transaction ID, and the Staging Table and Transaction Table names. To see the details of the transaction, use the Match Details link, which leads to the Matching Details form. Details aren't available if the transaction has already been unmatched or deleted.
To access the Transactions Duplicate Log form:
- Select Explorer in the navigation pane.
- Expand Fluence > Transaction Matching > Reports folders, and open the Transactions Duplicate Log form.
- In the Select Parameters dialog box, select the Transaction Table and Duplicates.
The fields in the Transactions Duplicate Log form are as follows:
| Field | Description |
| Timestamp | The time of transaction import that resulted in duplicate. |
| Transaction ID | This column retrieves its value from the ID column of the transaction table. |
| Match Details | Link to the Matching Details form. |
| Staging Table | Name of the Staging Table. |
| Transaction Table | Name of the Transaction Table. |
