Incremental Load in Transaction Matching - Same Records can prevail in each rounds
Summary:
We are loading data from Oracle ERP to ARCS Transaction matching for every 1 hour. This is a BIP Report integration where period is setup as param. In the Round 1 load we get certain profiles/intersections and in Round 2 we may get new profiles/or same profiles with plus or minus data.
Does TM support incremental data and if yes Merge ID will still work? Please note: At every round of hourly load, we may get same/new profiles data
Version (include the version you are using, if applicable):
25.10
Code Snippet (add any code snippets that support your topic, if applicable):
0