Systematically update transactions after loading
SummaryAbility to update attributes for a transaction after they have been loaded into TM
Wondering if there is a way to systematically update transactions in TM after they have been loaded into the application. In our application there are certain attributes that are updated up to 45 days after the transaction is initially created. Because this applies to thousands of transactions, we need a way to systematically update those attributes (client currently has a custom application that does this).
We've currently got a process to extract the unmatched transactions through a report, load into a DM location (with logic to duplicate and reverse the transaction), and load back into ARCS. This allows us to create a new transaction that matches off against the original, leaving a net new transaction which is a copy of the original with the necessary attributes updated. We are running into an issue where we may need to update other attributes based on the target attribute created on the second load (effectively creating a 3rd loop of extracting and reloading transactions).