Unique Transaction IDs
Transaction IDs are not unique system wide
Content (please ensure you mask any confidential information):
Some users noticed that when using transaction matching, there are Transaction IDs being used in different match types. For instance, Match Type A has a transaction loaded to it and the transaction ID is 12345. Match Type B then has a transaction loaded to it and the transaction ID is also 12345. Are transaction IDs supposed to be unique from a system standpoint or only a Match Type standpoint?
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):